Diagnostics for transactional execution errors in reliable transactions

ABSTRACT

Gathering diagnostics during a transactional execution in a transactional memory environment, a transactional memory environment for performing transactional executions is provided. Included is identifying a first indicator, by a computer system, signaling a beginning instruction of a transaction comprising a plurality of instructions; generating, by the computer system, a computed digest based on the execution of at least one of the plurality of instructions; accumulating, by the computer system, a diagnostic data of the transaction based on the execution of the plurality of instructions; identifying, by the computer system, a second indicator associated with the plurality of instructions signaling an ending instruction of the transaction comprising the plurality of instructions; and based on an abort of the transaction, not saving the memory store data of the transaction to memory.

BACKGROUND

This disclosure relates generally to transactional memory systems andmore specifically to a method, computer program and computer system forgathering transactional execution diagnostics using digests.

The number of central processing unit (CPU) cores on a chip and thenumber of CPU cores connected to a shared memory continues to growsignificantly to support growing workload capacity demand. Theincreasing number of CPUs cooperating to process the same workloads putsa significant burden on software scalability; for example, shared queuesor data-structures protected by traditional semaphores become hot spotsand lead to sub-linear n-way scaling curves. Traditionally this has beencountered by implementing finer-grained locking in software, and withlower latency/higher bandwidth interconnects in hardware. Implementingfine-grained locking to improve software scalability can be verycomplicated and error-prone, and at today's CPU frequencies, thelatencies of hardware interconnects are limited by the physicaldimension of the chips and systems, and by the speed of light.

Implementations of hardware Transactional Memory (TM) have beenintroduced, wherein a group of instructions, called a transaction,operate atomically and in isolation (sometimes called “serializability”)on a data structure in memory. The transaction executes optimisticallywithout obtaining a lock, but may need to abort and retry thetransaction execution if an operation, of the executing transaction, ona memory location conflicts with another operation on the same memorylocation. Previously, software transactional memory implementations havebeen proposed to support software Transactional Memory (TM). However,hardware TM can provide improved performance aspects and ease of useover software TM.

Publication by Song et al. titled “Error Detection by RedundantTransaction in Transactional Memory System” published in the Sixth IEEEInternational Conference on Networking, Architecture, and Storage (NAS),July 2011 by the IEEE Computer Society and incorporated by referenceherein teaches the issue of error detection in transactional memory, andproposes a new method of error detection based on redundant transaction(EDRT). This method creates a transaction copy for every transaction,and executes both original transactions and transaction copies onadequate processor cores, and achieves error detection by comparing theexecution results. EDRT utilizes the data-versioning mechanism oftransactional memory to achieve the acquisition of an approximateminimum error detection comparing data set, and the acquisition istransparent and online. At last, this paper validates the EDRT through 5test programs, including 4 SPLASH-2 benchmarks. The experimental resultsshow that, the average error detecting cost is about 3.68% relative tothe whole program, and it's only about 12.07% relative to thetransaction parts of the program.

U.S. Pat. No. 8,281,185 titled “Advice-Based Feedback For TransactionalExecution” filed 2009 Jun. 30 and incorporated by reference hereinteaches a system that facilitates the execution of a transaction for aprogram in a hardware-supported transactional memory system. Duringoperation, the system records a failure state of the transaction duringexecution of the transaction using hardware transactional memorymechanisms. Next, the system detects a transaction failure associatedwith the transaction. Finally, the system provides an advice stateassociated with the recorded failure state to the program to facilitatea response to the transaction failure by the program.

SUMMARY

According to an embodiment of the disclosure, a method for gatheringdiagnostics during a transactional execution in a transactional memoryenvironment for performing transactional executions, wherein memorystore data of a transaction are committed to memory at transactioncompletion, the transactional memory environment may be provided. Themethod may include identifying, by a computer system, a first indicator,wherein the computer system may be configured to identify the firstindicator. The first indicator may signal a beginning instruction of atransaction comprising a plurality of instructions. The method mayadditionally include generating, by the computer system, a computeddigest based on the execution of at least one of the plurality ofinstructions; accumulating, by the computer system, a diagnostic data ofthe transaction based on the execution of the plurality of instructions;identifying, by the computer system, a second indicator associated withthe plurality of instructions, the second indicator signaling an endinginstruction of the transaction comprising the plurality of instructions;and based on an abort of the transaction, not saving the memory storedata of the transaction to memory.

In another embodiment of the disclosure, a computer program product forgathering diagnostics during a transactional execution in atransactional memory environment for performing transactionalexecutions, wherein memory store data of a transaction are committed tomemory at transaction completion, the computer program product may beprovided. The computer program product may include a computer readablestorage medium readable by a processing circuit and storing instructionsfor execution by the processing circuit for performing a methodincluding: identifying, by a computer system, a first indicator, whereinthe computer system may be configured to identify the first indicator.The first indicator may signal a beginning instruction of a transactioncomprising a plurality of instructions. The method may additionallyinclude generating, by the computer system, a computed digest based onthe execution of at least one of the plurality of instructions;accumulating, by the computer system, a diagnostic data of thetransaction based on the execution of the plurality of instructions;identifying, by the computer system, a second indicator associated withthe plurality of instructions, the second indicator signaling an endinginstruction of the transaction comprising the plurality of instructions;and based on an abort of the transaction, not saving the memory storedata of the transaction to memory.

In another embodiment of the disclosure, a computer system for gatheringdiagnostics during a transactional execution in a transactional memoryenvironment for performing transactional executions, wherein memorystore data of a transaction are committed to memory at transactioncompletion, the computer system may be provided. The computer system mayinclude: a memory and a processor in communication with the memory,wherein the computer system is configured to perform a method, saidmethod including: identifying, by a computer system, a first indicator,wherein the computer system may be configured to identify the firstindicator. The first indicator may signal a beginning instruction of atransaction comprising a plurality of instructions. The method mayadditionally include generating, by the computer system, a computeddigest based on the execution of at least one of the plurality ofinstructions; accumulating, by the computer system, a diagnostic data ofthe transaction based on the execution of the plurality of instructions;identifying, by the computer system, a second indicator associated withthe plurality of instructions, the second indicator signaling an endinginstruction of the transaction comprising the plurality of instructions;and based on an abort of the transaction, not saving the memory storedata of the transaction to memory.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

One or more aspects of the present invention are particularly pointedout and distinctly claimed as examples in the claims at the conclusionof the specification. The foregoing and other objects, features, andadvantages of the invention are apparent from the following detaileddescription taken in conjunction with the accompanying drawings inwhich:

FIG. 1 depicts an example multicore Transactional Memory environment, inaccordance with an illustrative embodiment;

FIG. 2 depicts en example multicore Transactional memory environment, inaccordance with an illustrative embodiment;

FIG. 3 depicts example components of an example CPU, in accordance withan illustrative embodiment;

FIG. 4 is a flowchart illustrating steps performed by a processor forensuring the correct execution of a transaction during areliable-execution transactional execution, illustrated within the dataprocessing environment of FIG. 16, in accordance with an embodiment ofthe disclosure;

FIG. 5 is a schematic block diagram illustrating parallel execution ofthe reliable-execution transaction within the data processingenvironment of FIG. 16, in accordance with an embodiment of thedisclosure;

FIG. 6 is a schematic block diagram illustrating parallel execution ofthe reliable-execution transaction within the data processingenvironment of FIG. 16, in accordance with an embodiment of thedisclosure;

FIG. 7 is a flowchart illustrating steps performed by a processor forgenerating a digest at the end of a transactional execution, illustratedwithin the data processing environment of FIG. 16, in accordance with anembodiment of the disclosure;

FIG. 8 is a block diagram depicting an exemplary instruction forsignaling the beginning of a digest transaction, in accordance with anembodiment of the disclosure;

FIG. 9 is a block diagram depicting an exemplary instruction forsignaling the end of a digest transaction, in accordance with anembodiment of the disclosure;

FIG. 10 is a block diagram depicting an exemplary instruction forsignaling the beginning of a digest transaction, in accordance with anembodiment of the disclosure;

FIG. 11 is a block diagram depicting an exemplary instruction forsignaling the end of a digest transaction, in accordance with anembodiment of the disclosure;

FIG. 12 is a block diagram depicting an exemplary instruction forsignaling the beginning of a digest transaction, in accordance with anembodiment of the disclosure;

FIG. 13 is a block diagram depicting an exemplary instruction forsignaling the end of a digest transaction, in accordance with anembodiment of the disclosure;

FIG. 14 is a block diagram depicting an exemplary instruction forincluding specific data in a digest or for starting and ending digestgeneration during the transactional execution, in accordance with anembodiment of the disclosure;

FIG. 15 is a flowchart illustrating steps performed by a processor forgenerating a digest for transactions that include transactional nesting,illustrated within the data processing environment of FIG. 16, inaccordance with an embodiment of the disclosure;

FIG. 16 is a schematic block diagram which illustrates internal andexternal components of a server computer in accordance with anillustrative embodiment; and

FIG. 17 depicts an exemplary flow of gathering transactional executiondiagnostics using digests.

DETAILED DESCRIPTION

Historically, a computer system or processor had only a single processor(aka processing unit or central processing unit). The processor includedan instruction processing unit (IPU), a branch unit, a memory controlunit and the like. Such processors were capable of executing a singlethread of a program at a time. Operating systems were developed thatcould time-share a processor by dispatching a program to be executed onthe processor for a period of time, and then dispatching another programto be executed on the processor for another period of time. Astechnology evolved, memory subsystem caches were often added to theprocessor as well as complex dynamic address translation includingtranslation lookaside buffers (TLBs). The IPU itself was often referredto as a processor. As technology continued to evolve, an entireprocessor, could be packaged on a single semiconductor chip or die, sucha processor was referred to as a microprocessor. Then processors weredeveloped that incorporated multiple IPUs, such processors were oftenreferred to as multi-processors. Each such processor of amulti-processor computer system (processor) may include individual orshared caches, memory interfaces, system bus, address translationmechanism and the like. Virtual machine and instruction set architecture(ISA) emulators added a layer of software to a processor, that providedthe virtual machine with multiple “virtual processors” (aka processors)by time-slice usage of a single IPU in a single hardware processor. Astechnology further evolved, multi-threaded processors were developed,enabling a single hardware processor having a single multi-thread IPU toprovide a capability of simultaneously executing threads of differentprograms, thus each thread of a multi-threaded processor appeared to theoperating system as a processor. As technology further evolved, it waspossible to put multiple processors (each having an IPU) on a singlesemiconductor chip or die. These processors were referred to processorcores or just cores. Thus the terms such as processor, centralprocessing unit, processing unit, microprocessor, core, processor core,processor thread, and thread, for example, are often usedinterchangeably. Aspects of embodiments herein may be practiced by anyor all processors including those shown supra, without departing fromthe teachings herein. Wherein the term “thread” or “processor thread” isused herein, it is expected that particular advantage of the embodimentmay be had in a processor thread implementation.

Transaction Execution in Intel® Based Embodiments

In “Intel® Architecture Instruction Set Extensions ProgrammingReference” 319433-012A, February 2012, incorporated herein by referencein its entirety, Chapter 8 teaches, in part, that multithreadedapplications may take advantage of increasing numbers of CPU cores toachieve higher performance. However, the writing of multi-threadedapplications requires programmers to understand and take into accountdata sharing among the multiple threads. Access to shared data typicallyrequires synchronization mechanisms. These synchronization mechanismsare used to ensure that multiple threads update shared data byserializing operations that are applied to the shared data, oftenthrough the use of a critical section that is protected by a lock. Sinceserialization limits concurrency, programmers try to limit the overheaddue to synchronization.

Intel® Transactional Synchronization Extensions (Intel® TSX) allow aprocessor to dynamically determine whether threads need to be serializedthrough lock-protected critical sections, and to perform thatserialization only when required. This allows the processor to exposeand exploit concurrency that is hidden in an application because ofdynamically unnecessary synchronization.

With Intel TSX, programmer-specified code regions (also referred to as“transactional regions” or just “transactions”) are executedtransactionally. If the transactional execution completes successfully,then all memory operations performed within the transactional regionwill appear to have occurred instantaneously when viewed from otherprocessors. A processor makes the memory operations of the executedtransaction, performed within the transactional region, visible to otherprocessors only when a successful commit occurs, i.e., when thetransaction successfully completes execution. This process is oftenreferred to as an atomic commit.

Intel TSX provides two software interfaces to specify regions of codefor transactional execution. Hardware Lock Elision (HLE) is a legacycompatible instruction set extension (comprising the XACQUIRE andXRELEASE prefixes) to specify transactional regions. RestrictedTransactional Memory (RTM) is a new instruction set interface(comprising the XBEGIN, XEND, and XABORT instructions) for programmersto define transactional regions in a more flexible manner than thatpossible with HLE. HLE is for programmers who prefer the backwardcompatibility of the conventional mutual exclusion programming model andwould like to run HLE-enabled software on legacy hardware but would alsolike to take advantage of the new lock elision capabilities on hardwarewith HLE support. RTM is for programmers who prefer a flexible interfaceto the transactional execution hardware. In addition, Intel TSX alsoprovides an XTEST instruction. This instruction allows software to querywhether the logical processor is transactionally executing in atransactional region identified by either HLE or RTM.

Since a successful transactional execution ensures an atomic commit, theprocessor executes the code region optimistically without explicitsynchronization. If synchronization was unnecessary for that specificexecution, execution can commit without any cross-thread serialization.If the processor cannot commit atomically, then the optimistic executionfails. When this happens, the processor will roll back the execution, aprocess referred to as a transactional abort. On a transactional abort,the processor will discard all updates performed in the memory regionused by the transaction, restore architectural state to appear as if theoptimistic execution never occurred, and resume executionnon-transactionally.

A processor can perform a transactional abort for numerous reasons. Aprimary reason to abort a transaction is due to conflicting memoryaccesses between the transactionally executing logical processor andanother logical processor. Such conflicting memory accesses may preventa successful transactional execution. Memory addresses read from withina transactional region constitute the read-set of the transactionalregion and addresses written to within the transactional regionconstitute the write-set of the transactional region. Intel TSXmaintains the read- and write-sets at the granularity of a cache line. Aconflicting memory access occurs if another logical processor eitherreads a location that is part of the transactional region's write-set orwrites a location that is a part of either the read- or write-set of thetransactional region. A conflicting access typically means thatserialization is required for this code region. Since Intel TSX detectsdata conflicts at the granularity of a cache line, unrelated datalocations placed in the same cache line will be detected as conflictsthat result in transactional aborts. Transactional aborts may also occurdue to limited transactional resources. For example, the amount of dataaccessed in the region may exceed an implementation-specific capacity.Additionally, some instructions and system events may causetransactional aborts. Frequent transactional aborts result in wastedcycles and increased inefficiency.

Hardware Lock Elision

Hardware Lock Elision (HLE) provides a legacy compatible instruction setinterface for programmers to use transactional execution. HLE providestwo new instruction prefix hints: XACQUIRE and XRELEASE.

With HLE, a programmer adds the XACQUIRE prefix to the front of theinstruction that is used to acquire the lock that is protecting thecritical section. The processor treats the prefix as a hint to elide thewrite associated with the lock acquire operation. Even though the lockacquire has an associated write operation to the lock, the processordoes not add the address of the lock to the transactional region'swrite-set nor does it issue any write requests to the lock. Instead, theaddress of the lock is added to the read-set. The logical processorenters transactional execution. If the lock was available before theXACQUIRE prefixed instruction, then all other processors will continueto see the lock as available afterwards. Since the transactionallyexecuting logical processor neither added the address of the lock to itswrite-set nor performed externally visible write operations to the lock,other logical processors can read the lock without causing a dataconflict. This allows other logical processors to also enter andconcurrently execute the critical section protected by the lock. Theprocessor automatically detects any data conflicts that occur during thetransactional execution and will perform a transactional abort ifnecessary.

Even though the eliding processor did not perform any external writeoperations to the lock, the hardware ensures program order of operationson the lock. If the eliding processor itself reads the value of the lockin the critical section, it will appear as if the processor had acquiredthe lock, i.e. the read will return the non-elided value. This behaviorallows an HLE execution to be functionally equivalent to an executionwithout the HLE prefixes.

An XRELEASE prefix can be added in front of an instruction that is usedto release the lock protecting a critical section. Releasing the lockinvolves a write to the lock. If the instruction is to restore the valueof the lock to the value the lock had prior to the XACQUIRE prefixedlock acquire operation on the same lock, then the processor elides theexternal write request associated with the release of the lock and doesnot add the address of the lock to the write-set. The processor thenattempts to commit the transactional execution.

With HLE, if multiple threads execute critical sections protected by thesame lock but they do not perform any conflicting operations on eachother's data, then the threads can execute concurrently and withoutserialization. Even though the software uses lock acquisition operationson a common lock, the hardware recognizes this, elides the lock, andexecutes the critical sections on the two threads without requiring anycommunication through the lock—if such communication was dynamicallyunnecessary.

If the processor is unable to execute the region transactionally, thenthe processor will execute the region non-transactionally and withoutelision. HLE enabled software has the same forward progress guaranteesas the underlying non-HLE lock-based execution. For successful HLEexecution, the lock and the critical section code must follow certainguidelines. These guidelines only affect performance; and failure tofollow these guidelines will not result in a functional failure.Hardware without HLE support will ignore the XACQUIRE and XRELEASEprefix hints and will not perform any elision since these prefixescorrespond to the REPNE/REPE IA-32 prefixes which are ignored on theinstructions where XACQUIRE and XRELEASE are valid. Importantly, HLE iscompatible with the existing lock-based programming model. Improper useof hints will not cause functional bugs though it may expose latent bugsalready in the code.

Restricted Transactional Memory (RTM) provides a flexible softwareinterface for transactional execution. RTM provides three newinstructions—XBEGIN, XEND, and XABORT—for programmers to start, commit,and abort a transactional execution.

The programmer uses the XBEGIN instruction to specify the start of atransactional code region and the XEND instruction to specify the end ofthe transactional code region. If the RTM region could not besuccessfully executed transactionally, then the XBEGIN instruction takesan operand that provides a relative offset to the fallback instructionaddress.

A processor may abort RTM transactional execution for many reasons. Inmany instances, the hardware automatically detects transactional abortconditions and restarts execution from the fallback instruction addresswith the architectural state corresponding to that present at the startof the XBEGIN instruction and the EAX register updated to describe theabort status.

The XABORT instruction allows programmers to abort the execution of anRTM region explicitly. The XABORT instruction takes an 8-bit immediateargument that is loaded into the EAX register and will thus be availableto software following an RTM abort. RTM instructions do not have anydata memory location associated with them. While the hardware providesno guarantees as to whether an RTM region will ever successfully committransactionally, most transactions that follow the recommendedguidelines are expected to successfully commit transactionally. However,programmers must always provide an alternative code sequence in thefallback path to guarantee forward progress. This may be as simple asacquiring a lock and executing the specified code regionnon-transactionally. Further, a transaction that always aborts on agiven implementation may complete transactionally on a futureimplementation. Therefore, programmers must ensure the code paths forthe transactional region and the alternative code sequence arefunctionally tested.

Detection of HLE Support

A processor supports HLE execution if CPUID.07H.EBX.HLE [bit 4]=1.However, an application can use the HLE prefixes (XACQUIRE and XRELEASE)without checking whether the processor supports HLE. Processors withoutHLE support ignore these prefixes and will execute the code withoutentering transactional execution.

Detection of RTM Support

A processor supports RTM execution if CPUID.07H.EBX.RTM [bit 11]=1. Anapplication must check if the processor supports RTM before it uses theRTM instructions (XBEGIN, XEND, XABORT). These instructions willgenerate a #UD exception when used on a processor that does not supportRTM.

Detection of XTEST Instruction

A processor supports the XTEST instruction if it supports either HLE orRTM. An application must check either of these feature flags beforeusing the XTEST instruction. This instruction will generate a #UDexception when used on a processor that does not support either HLE orRTM.

Querying Transactional Execution Status

The XTEST instruction can be used to determine the transactional statusof a transactional region specified by HLE or RTM. Note, while the HLEprefixes are ignored on processors that do not support HLE, the XTESTinstruction will generate a #UD exception when used on processors thatdo not support either HLE or RTM.

Requirements for HLE Locks

For HLE execution to successfully commit transactionally, the lock mustsatisfy certain properties and access to the lock must follow certainguidelines.

An XRELEASE prefixed instruction must restore the value of the elidedlock to the value it had before the lock acquisition. This allowshardware to safely elide locks by not adding them to the write-set. Thedata size and data address of the lock release (XRELEASE prefixed)instruction must match that of the lock acquire (XACQUIRE prefixed) andthe lock must not cross a cache line boundary.

Software should not write to the elided lock inside a transactional HLEregion with any instruction other than an XRELEASE prefixed instruction,otherwise such a write may cause a transactional abort. In addition,recursive locks (where a thread acquires the same lock multiple timeswithout first releasing the lock) may also cause a transactional abort.Note that software can observe the result of the elided lock acquireinside the critical section. Such a read operation will return the valueof the write to the lock.

The processor automatically detects violations to these guidelines, andsafely transitions to a non-transactional execution without elision.Since Intel TSX detects conflicts at the granularity of a cache line,writes to data collocated on the same cache line as the elided lock maybe detected as data conflicts by other logical processors eliding thesame lock.

Transactional Nesting

Both HLE and RTM support nested transactional regions. However, atransactional abort restores state to the operation that startedtransactional execution: either the outermost XACQUIRE prefixed HLEeligible instruction or the outermost XBEGIN instruction. The processortreats all nested transactions as one transaction.

HLE Nesting and Elision

Programmers can nest HLE regions up to an implementation specific depthof MAX_HLE_NEST_COUNT. Each logical processor tracks the nesting countinternally but this count is not available to software. An XACQUIREprefixed HLE-eligible instruction increments the nesting count, and anXRELEASE prefixed HLE-eligible instruction decrements it. The logicalprocessor enters transactional execution when the nesting count goesfrom zero to one. The logical processor attempts to commit only when thenesting count becomes zero. A transactional abort may occur if thenesting count exceeds MAX_HLE_NEST_COUNT.

In addition to supporting nested HLE regions, the processor can alsoelide multiple nested locks. The processor tracks a lock for elisionbeginning with the XACQUIRE prefixed HLE eligible instruction for thatlock and ending with the XRELEASE prefixed HLE eligible instruction forthat same lock. The processor can, at any one time, track up to aMAX_HLE_ELIDED_LOCKS number of locks. For example, if the implementationsupports a MAX_HLE_ELIDED_LOCKS value of two and if the programmer neststhree HLE identified critical sections (by performing XACQUIRE prefixedHLE eligible instructions on three distinct locks without performing anintervening XRELEASE prefixed HLE eligible instruction on any one of thelocks), then the first two locks will be elided, but the third won't beelided (but will be added to the transaction's writeset). However, theexecution will still continue transactionally. Once an XRELEASE for oneof the two elided locks is encountered, a subsequent lock acquiredthrough the XACQUIRE prefixed HLE eligible instruction will be elided.

The processor attempts to commit the HLE execution when all elidedXACQUIRE and XRELEASE pairs have been matched, the nesting count goes tozero, and the locks have satisfied requirements. If execution cannotcommit atomically, then execution transitions to a non-transactionalexecution without elision as if the first instruction did not have anXACQUIRE prefix.

RTM Nesting

Programmers can nest RTM regions up to an implementation specificMAX_RTM_NEST_COUNT. The logical processor tracks the nesting countinternally but this count is not available to software. An XBEGINinstruction increments the nesting count, and an XEND instructiondecrements the nesting count. The logical processor attempts to commitonly if the nesting count becomes zero. A transactional abort occurs ifthe nesting count exceeds MAX_RTM_NEST_COUNT.

Nesting HLE and RTM

HLE and RTM provide two alternative software interfaces to a commontransactional execution capability. Transactional processing behavior isimplementation specific when HLE and RTM are nested together, e.g., HLEis inside RTM or RTM is inside HLE. However, in all cases, theimplementation will maintain HLE and RTM semantics. An implementationmay choose to ignore HLE hints when used inside RTM regions, and maycause a transactional abort when RTM instructions are used inside HLEregions. In the latter case, the transition from transactional tonon-transactional execution occurs seamlessly since the processor willre-execute the HLE region without actually doing elision, and thenexecute the RTM instructions.

Abort Status Definition

RTM uses the EAX register to communicate abort status to software.Following an RTM abort the EAX register has the following definition.

TABLE 1 RTM Abort Status Definition EAX Register Bit Position Meaning 0Set if abort caused by XABORT instruction 1 If set, the transaction maysucceed on retry, this bit is always clear if bit 0 is set 2 Set ifanother logical processor conflicted with a memory address that was partof the transaction that aborted 3 Set if an internal buffer overflowed 4Set if a debug breakpoint was hit 5 Set if an abort occurred duringexecution of a nested transaction 23:6 Reserved 31-24 XABORT argument(only valid if bit 0 set, otherwise reserved)

The EAX abort status for RTM only provides causes for aborts. It doesnot by itself encode whether an abort or commit occurred for the RTMregion. The value of EAX can be 0 following an RTM abort. For example, aCPUID instruction when used inside an RTM region causes a transactionalabort and may not satisfy the requirements for setting any of the EAXbits. This may result in an EAX value of 0.

RTM Memory Ordering

A successful RTM commit causes all memory operations in the RTM regionto appear to execute atomically. A successfully committed RTM regionconsisting of an XBEGIN followed by an XEND, even with no memoryoperations in the RTM region, has the same ordering semantics as a LOCKprefixed instruction.

The XBEGIN instruction does not have fencing semantics. However, if anRTM execution aborts, then all memory updates from within the RTM regionare discarded and are not made visible to any other logical processor.

RTM-Enabled Debugger Support

By default, any debug exception inside an RTM region will cause atransactional abort and will redirect control flow to the fallbackinstruction address with architectural state recovered and bit 4 in EAXset. However, to allow software debuggers to intercept execution ondebug exceptions, the RTM architecture provides additional capability.

If bit 11 of DR7 and bit 15 of the IA32_DEBUGCTL_MSR are both 1, any RTMabort due to a debug exception (#DB) or breakpoint exception (#BP)causes execution to roll back and restart from the XBEGIN instructioninstead of the fallback address. In this scenario, the EAX register willalso be restored back to the point of the XBEGIN instruction.

Programming Considerations

Typical programmer-identified regions are expected to transactionallyexecute and commit successfully. However, Intel TSX does not provide anysuch guarantee. A transactional execution may abort for many reasons. Totake full advantage of the transactional capabilities, programmersshould follow certain guidelines to increase the probability of theirtransactional execution committing successfully.

This section discusses various events that may cause transactionalaborts. The architecture ensures that updates performed within atransaction that subsequently aborts execution will never becomevisible. Only committed transactional executions initiate an update tothe architectural state. Transactional aborts never cause functionalfailures and only affect performance.

Instruction Based Considerations

Programmers can use any instruction safely inside a transaction (HLE orRTM) and can use transactions at any privilege level. However, someinstructions will always abort the transactional execution and causeexecution to seamlessly and safely transition to a non-transactionalpath.

Intel TSX allows for most common instructions to be used insidetransactions without causing aborts. The following operations inside atransaction do not typically cause an abort:

-   -   Operations on the instruction pointer register, general purpose        registers (GPRs) and the status flags (CF, OF, SF, PF, AF, and        ZF); and    -   Operations on XMM and YMM registers and the MXCSR register.

However, programmers must be careful when intermixing SSE and AVXoperations inside a transactional region. Intermixing SSE instructionsaccessing XMM registers and AVX instructions accessing YMM registers maycause transactions to abort. Programmers may use REP/REPNE prefixedstring operations inside transactions. However, long strings may causeaborts. Further, the use of CLD and STD instructions may cause aborts ifthey change the value of the DF flag. However, if DF is 1, the STDinstruction will not cause an abort. Similarly, if DF is 0, then the CLDinstruction will not cause an abort.

Instructions not enumerated here as causing abort when used inside atransaction will typically not cause a transaction to abort (examplesinclude but are not limited to MFENCE, LFENCE, SFENCE, RDTSC, RDTSCP,etc.).

The following instructions will abort transactional execution on anyimplementation:

XABORT

CPUID

PAUSE

In addition, in some implementations, the following instructions mayalways cause transactional aborts. These instructions are not expectedto be commonly used inside typical transactional regions. However,programmers must not rely on these instructions to force a transactionalabort, since whether they cause transactional aborts is implementationdependent.

-   -   Operations on X87 and MMX architecture state. This includes all        MMX and X87 instructions, including the FXRSTOR and FXSAVE        instructions.    -   Update to non-status portion of EFLAGS: CLI, STI, POPFD, POPFQ,        CLTS.    -   Instructions that update segment registers, debug registers        and/or control registers:    -   MOV to DS/ES/FS/GS/SS, POP DS/ES/FS/GS/SS, LDS, LES, LFS, LGS,        LSS, SWAPGS, WRFSBASE, WRGSBASE, LGDT, SGDT, LIDT, SIDT, LLDT,        SLDT, LTR, STR, Far CALL, Far JMP, Far RET, IRET, MOV to DRx,        MOV to CR0/CR2/CR3/CR4/CR8 and LMSW.    -   Ring transitions: SYSENTER, SYSCALL, SYSEXIT, and SYSRET.    -   TLB and Cacheability control: CLFLUSH, INVD, WBINVD, INVLPG,        INVPCID, and memory instructions with a non-temporal hint        (MOVNTDQA, MOVNTDQ, MOVNTI, MOVNTPD, MOVNTPS, and MOVNTQ).    -   Processor state save: XSAVE, XSAVEOPT, and XRSTOR.    -   Interrupts: INTn, INTO.    -   IO: IN, INS, REP INS, OUT, OUTS, REP OUTS and their variants.    -   VMX: VMPTRLD, VMPTRST, VMCLEAR, VMREAD, VMWRITE, VMCALL,        VMLAUNCH, VMRESUME, VMXOFF, VMXON, INVEPT, and INVVPID.    -   SMX: GETSEC.    -   UD2, RSM, RDMSR, WRMSR, HLT, MONITOR, MWAIT, XSETBV, VZEROUPPER,        MASKMOVQ, and V/MASKMOVDQU.        Runtime Considerations

In addition to the instruction-based considerations, runtime events maycause transactional execution to abort. These may be due to data accesspatterns or micro-architectural implementation features. The followinglist is not a comprehensive discussion of all abort causes.

Any fault or trap in a transaction that must be exposed to software willbe suppressed. Transactional execution will abort and execution willtransition to a non-transactional execution, as if the fault or trap hadnever occurred. If an exception is not masked, then that un-maskedexception will result in a transactional abort and the state will appearas if the exception had never occurred.

Synchronous exception events (#DE, #OF, #NP, #SS, #GP, #BR, #UD, #AC,#XF, #PF, #NM, #TS, #MF, #DB, #BP/INT3) that occur during transactionalexecution may cause an execution not to commit transactionally, andrequire a non-transactional execution. These events are suppressed as ifthey had never occurred. With HLE, since the non-transactional code pathis identical to the transactional code path, these events will typicallyre-appear when the instruction that caused the exception is re-executednon-transactionally, causing the associated synchronous events to bedelivered appropriately in the non-transactional execution. Asynchronousevents (NMI, SMI, INTR, IPI, PMI, etc.) occurring during transactionalexecution may cause the transactional execution to abort and transitionto a non-transactional execution. The asynchronous events will be pendedand handled after the transactional abort is processed.

Transactions only support write-back cacheable memory type operations. Atransaction may always abort if the transaction includes operations onany other memory type. This includes instruction fetches to UC memorytype.

Memory accesses within a transactional region may require the processorto set the Accessed and Dirty flags of the referenced page table entry.The behavior of how the processor handles this is implementationspecific. Some implementations may allow the updates to these flags tobecome externally visible even if the transactional region subsequentlyaborts. Some Intel TSX implementations may choose to abort thetransactional execution if these flags need to be updated. Further, aprocessor's page-table walk may generate accesses to its owntransactionally written but uncommitted state. Some Intel TSXimplementations may choose to abort the execution of a transactionalregion in such situations. Regardless, the architecture ensures that, ifthe transactional region aborts, then the transactionally written statewill not be made architecturally visible through the behavior ofstructures such as TLBs.

Executing self-modifying code transactionally may also causetransactional aborts. Programmers must continue to follow the Intelrecommended guidelines for writing self-modifying and cross-modifyingcode even when employing HLE and RTM. While an implementation of RTM andHLE will typically provide sufficient resources for executing commontransactional regions, implementation constraints and excessive sizesfor transactional regions may cause a transactional execution to abortand transition to a non-transactional execution. The architectureprovides no guarantee of the amount of resources available to dotransactional execution and does not guarantee that a transactionalexecution will ever succeed.

Conflicting requests to a cache line accessed within a transactionalregion may prevent the transaction from executing successfully. Forexample, if logical processor P0 reads line A in a transactional regionand another logical processor P1 writes line A (either inside or outsidea transactional region) then logical processor P0 may abort if logicalprocessor P1's write interferes with processor P0's ability to executetransactionally.

Similarly, if P0 writes line A in a transactional region and P1 reads orwrites line A (either inside or outside a transactional region), then P0may abort if P1's access to line A interferes with P0's ability toexecute transactionally. In addition, other coherence traffic may attimes appear as conflicting requests and may cause aborts. While thesefalse conflicts may happen, they are expected to be uncommon. Theconflict resolution policy to determine whether P0 or P1 aborts in theabove scenarios is implementation specific.

Generic Transaction Execution Embodiments:

According to “ARCHITECTURES FOR TRANSACTIONAL MEMORY”, a dissertationsubmitted to the Department of Computer Science and the Committee onGraduate Studies of Stanford University in partial fulfillment of therequirements for the Degree of Doctor of Philosophy, by Austen McDonald,June 2009, incorporated by reference herein in its entirety,fundamentally, there are three mechanisms needed to implement an atomicand isolated transactional region: versioning, conflict detection, andcontention management.

To make a transactional code region appear atomic, all the modificationsperformed by that transactional code region must be stored and keptisolated from other transactions until commit time. The system does thisby implementing a versioning policy. Two versioning paradigms exist:eager and lazy. An eager versioning system stores newly generatedtransactional values in place and stores previous memory values on theside, in what is called an undo-log. A lazy versioning system stores newvalues temporarily in what is called a write buffer, copying them tomemory only on commit. In either system, the cache is used to optimizestorage of new versions.

To ensure serializability between transactions, conflicts must bedetected and resolved. The two systems, i.e., the eager and lazyversioning systems, detect conflicts by implementing a conflictdetection policy, either optimistic or pessimistic. An optimistic systemexecutes transactions in parallel, checking for conflicts only when atransaction commits. A pessimistic system checks for conflicts at eachload and store. Similar to versioning, conflict detection also uses thecache, marking each line as either part of the read-set, part of thewrite-set, or both. The two systems resolve conflicts by implementing acontention management policy. Many contention management policies exist,some are more appropriate for optimistic conflict detection and some aremore appropriate for pessimistic. Described below are some examplepolicies.

Since each transactional memory (TM) system needs both versioningdetection and conflict detection, these options give rise to fourdistinct TM designs: Eager-Pessimistic (EP), Eager-Optimistic (EO),Lazy-Pessimistic (LP), and Lazy-Optimistic (LO). Table 2 brieflydescribes all four distinct TM designs.

FIGS. 1 and 2 depict an example of a multicore TM environment. FIG. 1shows many TM-enabled CPUs (CPU1 114 a, CPU2 114 b, etc.) on one die100, connected with an interconnect 122, under management of aninterconnect control 120 a, 120 b. Each CPU 114 a, 114 b (also known asa Processor) may have a split cache consisting of an Instruction Cache116 a, 116 b for caching instructions from memory to be executed and aData Cache 118 a, 118 b with TM support for caching data (operands) ofmemory locations to be operated on by CPU 114 a, 114 b (in FIG. 1, eachCPU 114 a, 114 b and its associated caches are referenced as 112 a, 112b). In an implementation, caches of multiple dies 100 are interconnectedto support cache coherency between the caches of the multiple dies 100.In an implementation, a single cache, rather than the split cache isemployed holding both instructions and data. In implementations, the CPUcaches are one level of caching in a hierarchical cache structure. Forexample each die 100 may employ a shared cache 124 to be shared amongstall the CPUs on the die 100. In another implementation, each die mayhave access to a shared cache 124, shared amongst all the processors ofall the dies 100.

FIG. 2 shows the details of an example transactional CPU environment112, having a CPU 114, including additions to support TM. Thetransactional CPU (processor) 114 may include hardware for supportingRegister Checkpoints 126 and special TM Registers 128. The transactionalCPU cache may have the MESI bits 130, Tags 140 and Data 142 of aconventional cache but also, for example, R bits 132 showing a line hasbeen read by the CPU 114 while executing a transaction and W bits 138showing a line has been written-to by the CPU 114 while executing atransaction.

A key detail for programmers in any TM system is how non-transactionalaccesses interact with transactions. By design, transactional accessesare screened from each other using the mechanisms above. However, theinteraction between a regular, non-transactional load with a transactioncontaining a new value for that address must still be considered. Inaddition, the interaction between a non-transactional store with atransaction that has read that address must also be explored. These areissues of the database concept isolation.

A TM system is said to implement strong isolation, sometimes calledstrong atomicity, when every non-transactional load and store acts likean atomic transaction. Therefore, non-transactional loads cannot seeuncommitted data and non-transactional stores cause atomicity violationsin any transactions that have read that address. A system where this isnot the case is said to implement weak isolation, sometimes called weakatomicity.

Strong isolation is often more desirable than weak isolation due to therelative ease of conceptualization and implementation of strongisolation. Additionally, if a programmer has forgotten to surround someshared memory references with transactions, causing bugs, then withstrong isolation, the programmer will often detect that oversight usinga simple debug interface because the programmer will see anon-transactional region causing atomicity violations. Also, programswritten in one model may work differently on another model.

Further, strong isolation is often easier to support in hardware TM thanweak isolation. With strong isolation, since the coherence protocolalready manages load and store communication between processors,transactions can detect non-transactional loads and stores and actappropriately. To implement strong isolation in software TransactionalMemory (TM), non-transactional code must be modified to include read-and write-barriers; potentially crippling performance. Although greateffort has been expended to remove many un-needed barriers, suchtechniques are often complex and performance is typically far lower thanthat of HTMs.

TABLE 2 Transactional Memory Design Space VERSIONING Lazy Eager CONFLICTOptimistic Storing updates in a write Not practical: waiting to updateDETECTION buffer; detecting conflicts at memory until commit time butcommit time. detecting conflicts at access time guarantees wasted workand provides no advantage Pessimistic Storing updates in a Updatingmemory, keeping old writebuffer; detecting values in undo log; detectingconflicts at access time. conflicts at access time.

Table 2 illustrates the fundamental design space of transactional memory(versioning and conflict detection).

Eager-Pessimistic (EP)

This first TM design described below is known as Eager-Pessimistic. AnEP system stores its write-set “in place” (hence the name “eager”) and,to support rollback, stores the old values of overwritten lines in an“undo log”. Processors use the W 138 and R 132 cache bits to track readand write-sets and detect conflicts when receiving snooped loadrequests. Perhaps the most notable examples of EP systems in knownliterature are LogTM and UTM.

Beginning a transaction in an EP system is much like beginning atransaction in other systems: tm_begin( ) takes a register checkpoint,and initializes any status registers. An EP system also requiresinitializing the undo log, the details of which are dependent on the logformat, but often involve initializing a log base pointer to a region ofpre-allocated, thread-private memory, and clearing a log boundsregister.

Versioning: In EP, due to the way eager versioning is designed tofunction, the MESI 130 state transitions (cache line indicatorscorresponding to Modified, Exclusive, Shared, and Invalid code states)are left mostly unchanged. Outside of a transaction, the MESI 130 statetransitions are left completely unchanged. When reading a line inside atransaction, the standard coherence transitions apply (S (Shared)→S, I(Invalid)→S, or I→E (Exclusive)), issuing a load miss as needed, but theR 132 bit is also set. Likewise, writing a line applies the standardtransitions (S→M, E→I, I→M), issuing a miss as needed, but also sets theW 138 (Written) bit. The first time a line is written, the old versionof the entire line is loaded then written to the undo log to preserve itin case the current transaction aborts. The newly written data is thenstored “in-place,” over the old data.

Conflict Detection: Pessimistic conflict detection uses coherencemessages exchanged on misses, or upgrades, to look for conflicts betweentransactions. When a read miss occurs within a transaction, otherprocessors receive a load request; but they ignore the request if theydo not have the needed line. If the other processors have the neededline non-speculatively or have the line R 132 (Read), they downgradethat line to S, and in certain cases issue a cache-to-cache transfer ifthey have the line in MESI's 130 M or E state. However, if the cache hasthe line W 138, then a conflict is detected between the two transactionsand additional action(s) must be taken.

Similarly, when a transaction seeks to upgrade a line from shared tomodified (on a first write), the transaction issues an exclusive loadrequest, which is also used to detect conflicts. If a receiving cachehas the line non-speculatively, then the line is invalidated, and incertain cases a cache-to-cache transfer (M or E states) is issued. But,if the line is R 132 or W 138, a conflict is detected.

Validation: Because conflict detection is performed on every load, atransaction always has exclusive access to its own write-set. Therefore,validation does not require any additional work.

Commit: Since eager versioning stores the new version of data items inplace, the commit process simply clears the W 138 and R 132 bits anddiscards the undo log.

Abort: When a transaction rolls back, the original version of each cacheline in the undo log must be restored, a process called “unrolling” or“applying” the log. This is done during tm_discard( ) and must be atomicwith regard to other transactions. Specifically, the write-set muststill be used to detect conflicts: this transaction has the only correctversion of lines in its undo log, and requesting transactions must waitfor the correct version to be restored from that log. Such a log can beapplied using a hardware state machine or software abort handler.

Eager-Pessimistic has the characteristics of: Commit is simple and sinceit is in-place, very fast. Similarly, validation is a no-op. Pessimisticconflict detection detects conflicts early, thereby reducing the numberof “doomed” transactions. For example, if two transactions are involvedin a Write-After-Read dependency, then that dependency is detectedimmediately in pessimistic conflict detection. However, in optimisticconflict detection such conflicts are not detected until the writercommits.

Eager-Pessimistic also has the characteristics of: As described above,the first time a cache line is written, the old value must be written tothe log, incurring extra cache accesses. Aborts are expensive as theyrequire undoing the log. For each cache line in the log, a load must beissued, perhaps going as far as main memory before continuing to thenext line. Pessimistic conflict detection also prevents certainserializable schedules from existing.

Additionally, because conflicts are handled as they occur, there is apotential for livelock and careful contention management mechanisms mustbe employed to guarantee forward progress.

Lazy-Optimistic (LO)

Another popular TM design is Lazy-Optimistic (LO), which stores itswrite-set in a “write buffer” or “redo log” and detects conflicts atcommit time (still using the R 132 and W 138 bits).

Versioning: Just as in the EP system, the MESI protocol of the LO designis enforced outside of the transactions. Once inside a transaction,reading a line incurs the standard MESI transitions but also sets the R132 bit. Likewise, writing a line sets the W 138 bit of the line, buthandling the MESI transitions of the LO design is different from that ofthe EP design. First, with lazy versioning, the new versions of writtendata are stored in the cache hierarchy until commit while othertransactions have access to old versions available in memory or othercaches. To make available the old versions, dirty lines (M lines) mustbe evicted when first written by a transaction. Second, no upgrademisses are needed because of the optimistic conflict detection feature:if a transaction has a line in the S state, it can simply write to itand upgrade that line to an M state without communicating the changeswith other transactions because conflict detection is done at committime.

Conflict Detection and Validation: To validate a transaction and detectconflicts, LO communicates the addresses of speculatively modified linesto other transactions only when it is preparing to commit. Onvalidation, the processor sends one, potentially large, network packetcontaining all the addresses in the write-set. Data is not sent, butleft in the cache of the committer and marked dirty (M). To build thispacket without searching the cache for lines marked W, a simple bitvector is used, called a “store buffer,” with one bit per cache line totrack these speculatively modified lines. Other transactions use thisaddress packet to detect conflicts: if an address is found in the cacheand the R 132 and/or W 138 bits are set, then a conflict is initiated.If the line is found but neither R 132 nor W 138 is set, then the lineis simply invalidated, which is similar to processing an exclusive load.

To support transaction atomicity, these address packets must be handledatomically, i.e., no two address packets may exist at once with the sameaddresses. In an LO system, this can be achieved by simply acquiring aglobal commit token before sending the address packet. However, atwo-phase commit scheme could be employed by first sending out theaddress packet, collecting responses, enforcing an ordering protocol(perhaps oldest transaction first), and committing once all responsesare satisfactory.

Commit: Once validation has occurred, commit needs no special treatment:simply clear W 138 and R 132 bits and the store buffer. Thetransaction's writes are already marked dirty in the cache and othercaches' copies of these lines have been invalidated via the addresspacket. Other processors can then access the committed data through theregular coherence protocol.

Abort: Rollback is equally easy: because the write-set is containedwithin the local caches, these lines can be invalidated, then clear W138 and R 132 bits and the store buffer. The store buffer allows W linesto be found to invalidate without the need to search the cache.

Lazy-Optimistic has the characteristics of: Aborts are very fast,requiring no additional loads or stores and making only local changes.More serializable schedules can exist than found in EP, which allows anLO system to more aggressively speculate that transactions areindependent, which can yield higher performance. Finally, the latedetection of conflicts can increase the likelihood of forward progress.

Lazy-Optimistic also has the characteristics of: Validation takes globalcommunication time proportional to size of write set. Doomedtransactions can waste work since conflicts are detected only at committime.

Lazy-Pessimistic (LP)

Lazy-Pessimistic (LP) represents a third TM design option, sittingsomewhere between EP and LO: storing newly written lines in a writebuffer but detecting conflicts on a per access basis.

Versioning: Versioning is similar but not identical to that of LO:reading a line sets its R bit 132, writing a line sets its W bit 138,and a store buffer is used to track W lines in the cache. Also, dirty(M) lines must be evicted when first written by a transaction, just asin LO. However, since conflict detection is pessimistic, load exclusivesmust be performed when upgrading a transactional line from I, S→M, whichis unlike LO.

Conflict Detection: LP's conflict detection operates the same as EP's:using coherence messages to look for conflicts between transactions.

Validation: Like in EP, pessimistic conflict detection ensures that atany point, a running transaction has no conflicts with any other runningtransaction, so validation is a no-op.

Commit: Commit needs no special treatment: simply clear W 138 and R 132bits and the store buffer, like in LO.

Abort: Rollback is also like that of LO: simply invalidate the write-setusing the store buffer and clear the W and R bits and the store buffer.

Eager-Optimistic (EO)

The LP has the characteristics of: Like LO, aborts are very fast. LikeEP, the use of pessimistic conflict detection reduces the number of“doomed” transactions. Like EP, some serializable schedules are notallowed and conflict detection must be performed on each cache miss.

The final combination of versioning and conflict detection isEager-Optimistic (EO). EO may be a less than optimal choice for HTMsystems: since new transactional versions are written in-place, othertransactions have no choice but to notice conflicts as they occur (i.e.,as cache misses occur). But since EO waits until commit time to detectconflicts, those transactions become “zombies,” continuing to execute,wasting resources, yet are “doomed” to abort.

EO has proven to be useful in STMs and is implemented by Bartok-STM andMcRT. A lazy versioning STM needs to check its write buffer on each readto ensure that it is reading the most recent value. Since the writebuffer is not a hardware structure, this is expensive, hence thepreference for write-in-place eager versioning. Additionally, sincechecking for conflicts is also expensive in an STM, optimistic conflictdetection offers the advantage of performing this operation in bulk.

Contention Management

How a transaction rolls back once the system has decided to abort thattransaction has been described above, but, since a conflict involves twotransactions, the topics of which transaction should abort, how thatabort should be initiated, and when should the aborted transaction beretried need to be explored. These are topics that are addressed byContention Management (CM), a key component of transactional memory.Described below are policies regarding how the systems initiate abortsand the various established methods of managing which transactionsshould abort in a conflict.

Contention Management Policies

A Contention Management (CM) Policy is a mechanism that determines whichtransaction involved in a conflict should abort and when the abortedtransaction should be retried. For example, it is often the case thatretrying an aborted transaction immediately does not lead to the bestperformance. Conversely, employing a back-off mechanism, which delaysthe retrying of an aborted transaction, can yield better performance.STMs first grappled with finding the best contention management policiesand many of the policies outlined below were originally developed forSTMs.

CM Policies draw on a number of measures to make decisions, includingages of the transactions, size of read- and write-sets, the number ofprevious aborts, etc. The combinations of measures to make suchdecisions are endless, but certain combinations are described below,roughly in order of increasing complexity.

To establish some nomenclature, first note that in a conflict there aretwo sides: the attacker and the defender. The attacker is thetransaction requesting access to a shared memory location. Inpessimistic conflict detection, the attacker is the transaction issuingthe load or load exclusive. In optimistic, the attacker is thetransaction attempting to validate. The defender in both cases is thetransaction receiving the attacker's request.

An Aggressive CM Policy immediately and always retries either theattacker or the defender. In LO, Aggressive means that the attackeralways wins, and so Aggressive is sometimes called committer wins. Sucha policy was used for the earliest LO systems. In the case of EP,Aggressive can be either defender wins or attacker wins.

Restarting a conflicting transaction that will immediately experienceanother conflict is bound to waste work—namely interconnect bandwidthrefilling cache misses. A Polite CM Policy employs exponential backoff(but linear could also be used) before restarting conflicts. To preventstarvation, a situation where a process does not have resourcesallocated to it by the scheduler, the exponential backoff greatlyincreases the odds of transaction success after some n retries.

Another approach to conflict resolution is to randomly abort theattacker or defender (a policy called Randomized). Such a policy may becombined with a randomized backoff scheme to avoid unneeded contention.

However, making random choices, when selecting a transaction to abort,can result in aborting transactions that have completed “a lot of work”,which can waste resources. To avoid such waste, the amount of workcompleted on the transaction can be taken into account when determiningwhich transaction to abort. One measure of work could be a transaction'sage. Other methods include Oldest, Bulk TM, Size Matters, Karma, andPolka. Oldest is a simple timestamp method that aborts the youngertransaction in a conflict. Bulk TM uses this scheme. Size Matters islike Oldest but instead of transaction age, the number of read/writtenwords is used as the priority, reverting to Oldest after a fixed numberof aborts. Karma is similar, using the size of the write-set aspriority. Rollback then proceeds after backing off a fixed amount oftime. Aborted transactions keep their priorities after being aborted(hence the name Karma). Polka works like Karma but instead of backingoff a predefined amount of time, it backs off exponentially more eachtime.

Since aborting wastes work, it is logical to argue that stalling anattacker until the defender has finished their transaction would lead tobetter performance. Unfortunately, such a simple scheme easily leads todeadlock.

Deadlock avoidance techniques can be used to solve this problem. Greedyuses two rules to avoid deadlock. The first rule is, if a firsttransaction, T1, has lower priority than a second transaction, T0, or ifT1 is waiting for another transaction, then T1 aborts when conflictingwith T0. The second rule is, if T1 has higher priority than T0 and isnot waiting, then T0 waits until T1 commits, aborts, or starts waiting(in which case the first rule is applied). Greedy provides someguarantees about time bounds for executing a set of transactions. One EPdesign (LogTM) uses a CM policy similar to Greedy to achieve stallingwith conservative deadlock avoidance.

Example MESI coherency rules provide for four possible states in which acache line of a multiprocessor cache system may reside, M, E, S, and I,defined as follows:

Modified (M): The cache line is present only in the current cache, andis dirty; it has been modified from the value in main memory. The cacheis required to write the data back to main memory at some time in thefuture, before permitting any other read of the (no longer valid) mainmemory state. The write-back changes the line to the Exclusive state.

Exclusive (E): The cache line is present only in the current cache, butis clean; it matches main memory. It may be changed to the Shared stateat any time, in response to a read request. Alternatively, it may bechanged to the Modified state when writing to it.

Shared (S): Indicates that this cache line may be stored in other cachesof the machine and is “clean”; it matches the main memory. The line maybe discarded (changed to the Invalid state) at any time.

Invalid (I): Indicates that this cache line is invalid (unused).

TM coherency status indicators (R 132, W 138) may be provided for eachcache line, in addition to, or encoded in the MESI coherency bits. An R132 indicator indicates the current transaction has read from the dataof the cache line, and a W 138 indicator indicates the currenttransaction has written to the data of the cache line.

In another aspect of TM design, a system is designed using transactionalstore buffers. U.S. Pat. No. 6,349,361 titled “Methods and Apparatus forReordering and Renaming Memory References in a Multiprocessor ComputerSystem,” filed Mar. 31, 2000 and incorporated by reference herein in itsentirety, teaches a method for reordering and renaming memory referencesin a multiprocessor computer system having at least a first and a secondprocessor. The first processor has a first private cache and a firstbuffer, and the second processor has a second private cache and a secondbuffer. The method includes the steps of, for each of a plurality ofgated store requests received by the first processor to store a datum,exclusively acquiring a cache line that contains the datum by the firstprivate cache, and storing the datum in the first buffer. Upon the firstbuffer receiving a load request from the first processor to load aparticular datum, the particular datum is provided to the firstprocessor from among the data stored in the first buffer based on anin-order sequence of load and store operations. Upon the first cachereceiving a load request from the second cache for a given datum, anerror condition is indicated and a current state of at least one of theprocessors is reset to an earlier state when the load request for thegiven datum corresponds to the data stored in the first buffer.

The main implementation components of one such transactional memoryfacility are a transaction-backup register file for holdingpre-transaction GR (general register) content, a cache directory totrack the cache lines accessed during the transaction, a store cache tobuffer stores until the transaction ends, and firmware routines toperform various complex functions. In this section a detailedimplementation is described.

IBM zEnterprise EC12 Enterprise Server Embodiment

The IBM zEnterprise EC12 enterprise server introduces transactionalexecution (TX) in transactional memory, and is described in part in apaper, “Transactional Memory Architecture and Implementation for IBMSystem z” of Proceedings Pages 25-36 presented at MICRO-45, 1-5 Dec.2012, Vancouver, British Columbia, Canada, available from IEEE ComputerSociety Conference Publishing Services (CPS), which is incorporated byreference herein in its entirety.

Table 3 shows an example transaction. Transactions started with TBEGINare not assured to ever successfully complete with TEND, since they canexperience an aborting condition at every attempted execution, e.g., dueto repeating conflicts with other CPUs. This requires that the programsupport a fallback path to perform the same operationnon-transactionally, e.g., by using traditional locking schemes. Thisputs significant burden on the programming and software verificationteams, especially where the fallback path is not automatically generatedby a reliable compiler.

TABLE 3 Example Transaction Code LHI R0,0 *initialize retry count=0 loopTBEGIN *begin transaction JNZ abort *go to abort code if CC1=0 LT R1,lock *load and test the fallback lock JNZ lckbzy *branch if lock busy .. . perform operation . . . TEND *end transaction . . .  . . .  . . .  .. . lckbzy TABORT *abort if lock busy; this *resumes after TBEGIN abortJO fallback *no retry if CC=3 AHI R0, 1 *increment retry count CIJNLR0,6, fallback *give up after 6 attempts PPA R0, TX *random delay basedon retry count . . . potentially wait for lock to become free . . . Jloop *jump back to retry fallback OBTAIN lock *using Compare&Swap . . .perform operation . . . RELEASE lock . . .  . . .  . . .  . . .

The requirement of providing a fallback path for aborted TransactionExecution (TX) transactions can be onerous. Many transactions operatingon shared data structures are expected to be short, touch only a fewdistinct memory locations, and use simple instructions only. For thosetransactions, the IBM zEnterprise EC12 introduces the concept ofconstrained transactions; under normal conditions, the CPU 114 (FIG. 2)assures that constrained transactions eventually end successfully,albeit without giving a strict limit on the number of necessary retries.A constrained transaction starts with a TBEGINC instruction and endswith a regular TEND. Implementing a task as a constrained ornon-constrained transaction typically results in very comparableperformance, but constrained transactions simplify software developmentby removing the need for a fallback path. IBM's Transactional Executionarchitecture is further described in z/Architecture, Principles ofOperation, Tenth Edition, SA22-7832-09 published September 2012 fromIBM, incorporated by reference herein in its entirety.

A constrained transaction starts with the TBEGINC instruction. Atransaction initiated with TBEGINC must follow a list of programmingconstraints; otherwise the program takes a non-filterableconstraint-violation interruption. Exemplary constraints may include,but not be limited to: the transaction can execute a maximum of 32instructions, all instruction text must be within 256 consecutive bytesof memory; the transaction contains only forward-pointing relativebranches (i.e., no loops or subroutine calls); the transaction canaccess a maximum of 4 aligned octowords (an octoword is 32 bytes) ofmemory; and restriction of the instruction-set to exclude complexinstructions like decimal or floating-point operations. The constraintsare chosen such that many common operations like doubly linkedlist-insert/delete operations can be performed, including the verypowerful concept of atomic compare-and-swap targeting up to 4 alignedoctowords. At the same time, the constraints were chosen conservativelysuch that future CPU implementations can assure transaction successwithout needing to adjust the constraints, since that would otherwiselead to software incompatibility.

TBEGINC mostly behaves like XBEGIN in TSX or TBEGIN on IBM's zEC12servers, except that the floating-point register (FPR) control and theprogram interruption filtering fields do not exist and the controls areconsidered to be zero. On a transaction abort, the instruction addressis set back directly to the TBEGINC instead of to the instruction after,reflecting the immediate retry and absence of an abort path forconstrained transactions.

Nested transactions are not allowed within constrained transactions, butif a TBEGINC occurs within a non-constrained transaction it is treatedas opening a new non-constrained nesting level just like TBEGIN would.This can occur, e.g., if a non-constrained transaction calls asubroutine that uses a constrained transaction internally.

Since interruption filtering is implicitly off, all exceptions during aconstrained transaction lead to an interruption into the operatingsystem (OS). Eventual successful finishing of the transaction relies onthe capability of the OS to page-in the at most 4 pages touched by anyconstrained transaction. The OS must also ensure time-slices long enoughto allow the transaction to complete.

TABLE 4 Transaction Code Example TBEGINC *begin constrained transaction. . . perform operation . . . TEND    *end transaction

Table 4 shows the constrained-transactional implementation of the codein Table 3, assuming that the constrained transactions do not interactwith other locking-based code. No lock testing is shown therefore, butcould be added if constrained transactions and lock-based code weremixed.

When failure occurs repeatedly, software emulation is performed usingmillicode as part of system firmware. Advantageously, constrainedtransactions have desirable properties because of the burden removedfrom programmers.

With reference to FIG. 3, the IBM zEnterprise EC12 processor introducedthe transactional execution facility. The processor can decode 3instructions per clock cycle; simple instructions are dispatched assingle micro-ops, and more complex instructions are cracked intomultiple micro-ops. The micro-ops (Uops 232 b) are written into aunified issue queue 216, from where they can be issued out-of-order. Upto two fixed-point, one floating-point, two load/store, and two branchinstructions can execute every cycle. A Global Completion Table (GCT)232 holds every micro-op 232 b and a transaction nesting depth (TND) 232a. The GCT 232 is written in-order at decode time, tracks the executionstatus of each micro-op 232 b, and completes instructions when allmicro-ops 232 b of the oldest instruction group have successfullyexecuted.

The level 1 (L1) data cache 240 is a 96 KB (kilo-byte) 6-way associativecache with 256 byte cache-lines and 4 cycle use latency, coupled to aprivate 1 MB (mega-byte) 8-way associative 2nd-level (L2) data cache 268with 7 cycles use-latency penalty for L1 240 misses. The L1 240 cache isthe cache closest to a processor and Ln cache is a cache at the nthlevel of caching. Both L1 240 and L2 268 caches are store-through. Sixcores on each central processor (CP) chip share a 48 MB 3rd-levelstore-in cache, and six CP chips are connected to an off-chip 384 MB4th-level cache, packaged together on a glass ceramic multi-chip module(MCM). Up to 4 multi-chip modules (MCMs) can be connected to a coherentsymmetric multi-processor (SMP) system with up to 144 cores (not allcores are available to run customer workload).

Coherency is managed with a variant of the MESI protocol. Cache-linescan be owned read-only (shared) or exclusive; the L1 240 and L2 268 arestore-through and thus do not contain dirty lines. The L3 272 and L4caches (not shown) are store-in and track dirty states. Each cache isinclusive of all its connected lower level caches.

Coherency requests are called “cross interrogates” (XI) and are senthierarchically from higher level to lower-level caches, and between theL4s. When one core misses the L1 240 and L2 268 and requests the cacheline from its local L3 272, the L3 272 checks whether it owns the line,and if necessary sends an XI to the currently owning L2 268/L1 240 underthat L3 272 to ensure coherency, before it returns the cache line to therequestor. If the request also misses the L3 272, the L3 272 sends arequest to the L4 (not shown), which enforces coherency by sending XIsto all necessary L3s under that L4, and to the neighboring L4s. Then theL4 responds to the requesting L3 which forwards the response to the L2268/L1 240.

Note that due to the inclusivity rule of the cache hierarchy, sometimescache lines are XI'ed from lower-level caches due to evictions onhigher-level caches caused by associativity overflows from requests toother cache lines. These XIs can be called “LRU XIs”, where LRU standsfor least recently used.

Making reference to yet another type of XI requests, Demote-XIstransition cache-ownership from exclusive into read-only state, andExclusive-XIs transition cache ownership from exclusive into invalidstate. Demote-XIs and Exclusive-XIs need a response back to the XIsender. The target cache can “accept” the XI, or send a “reject”response if it first needs to evict dirty data before accepting the XI.The L1 240/L2 268 caches are store through, but may reject demote-XIsand exclusive XIs if they have stores in their store queues that need tobe sent to L3 before downgrading the exclusive state. A rejected XI willbe repeated by the sender. Read-only-XIs are sent to caches that own theline read-only; no response is needed for such XIs since they cannot berejected. The details of the SMP protocol are similar to those describedfor the IBM z10 by P. Mak, C. Walters, and G. Strait, in “IBM System z10processor cache subsystem microarchitecture”, IBM Journal of Researchand Development, Vol 53:1, 2009, which is incorporated by referenceherein in its entirety.

Transactional Instruction Execution

FIG. 3 depicts example components of an example transactional executionenvironment, including a CPU and caches/components with which itinteracts (such as those depicted in FIGS. 1 and 2). The instructiondecode unit 208 (IDU) keeps track of the current transaction nestingdepth 212 (TND). When the IDU 208 receives a TBEGIN instruction, thenesting depth 212 is incremented, and conversely decremented on TENDinstructions. The nesting depth 212 is written into the GCT 232 forevery dispatched instruction. When a TBEGIN or TEND is decoded on aspeculative path that later gets flushed, the IDU's 208 nesting depth212 is refreshed from the youngest GCT 232 entry that is not flushed.The transactional state is also written into the issue queue 216 forconsumption by the execution units, mostly by the Load/Store Unit (LSU)280, which also has an effective address calculator 236 is included inthe LSU 280. The TBEGIN instruction may specify a transaction diagnosticblock (TDB) for recording status information, should the transactionabort before reaching a TEND instruction.

Similar to the nesting depth, the IDU 208/GCT 232 collaboratively trackthe access register/floating-point register (AR/FPR) modification masksthrough the transaction nest; the IDU 208 can place an abort requestinto the GCT 232 when an AR/FPR-modifying instruction is decoded and themodification mask blocks that. When the instruction becomesnext-to-complete, completion is blocked and the transaction aborts.Other restricted instructions are handled similarly, including TBEGIN ifdecoded while in a constrained transaction, or exceeding the maximumnesting depth.

An outermost TBEGIN is cracked into multiple micro-ops depending on theGR-Save-Mask; each micro-op 232 b (including, for example uop 0, uop 1,and uop2) will be executed by one of the two fixed point units (FXUs)220 to save a pair of GRs 228 into a special transaction-backup registerfile 224, that is used to later restore the GR 228 content in case of atransaction abort. Also the TBEGIN spawns micro-ops 232 b to perform anaccessibility test for the TDB if one is specified; the address is savedin a special purpose register for later usage in the abort case. At thedecoding of an outermost TBEGIN, the instruction address and theinstruction text of the TBEGIN are also saved in special purposeregisters for a potential abort processing later on.

TEND and NTSTG are single micro-op 232 b instructions; NTSTG(non-transactional store) is handled like a normal store except that itis marked as non-transactional in the issue queue 216 so that the LSU280 can treat it appropriately. TEND is a no-op at execution time, theending of the transaction is performed when TEND completes.

As mentioned, instructions that are within a transaction are marked assuch in the issue queue 216, but otherwise execute mostly unchanged; theLSU 280 performs isolation tracking as described in the next section.

Since decoding is in-order, and since the IDU 208 keeps track of thecurrent transactional state and writes it into the issue queue 216 alongwith every instruction from the transaction, execution of TBEGIN, TEND,and instructions before, within, and after the transaction can beperformed out-of order. It is even possible (though unlikely) that TENDis executed first, then the entire transaction, and lastly the TBEGINexecutes. Program order is restored through the GCT 232 at completiontime. The length of transactions is not limited by the size of the GCT232, since general purpose registers (GRs) 228 can be restored from thebackup register file 224.

During execution, the program event recording (PER) events are filteredbased on the Event Suppression Control, and a PER TEND event is detectedif enabled. Similarly, while in transactional mode, a pseudo-randomgenerator may be causing the random aborts as enabled by the TransactionDiagnostics Control.

Tracking for Transactional Isolation

The Load/Store Unit 280 tracks cache lines that were accessed duringtransactional execution, and triggers an abort if an XI from another CPU(or an LRU-XI) conflicts with the footprint. If the conflicting XI is anexclusive or demote XI, the LSU 280 rejects the XI back to the L3 272 inthe hope of finishing the transaction before the L3 272 repeats the XI.This “stiff-arming” is very efficient in highly contended transactions.In order to prevent hangs when two CPUs stiff-arm each other, aXI-reject counter is implemented, which triggers a transaction abortwhen a threshold is met.

The L1 cache directory 240 is traditionally implemented with staticrandom access memories (SRAMs). For the transactional memoryimplementation, the valid bits 244 (64 rows×6 ways) of the directoryhave been moved into normal logic latches, and are supplemented with twomore bits per cache line: the TX-read 248 and TX-dirty 252 bits.

The TX-read 248 bits are reset when a new outermost TBEGIN is decoded(which is interlocked against a prior still pending transaction). TheTX-read 248 bit is set at execution time by every load instruction thatis marked “transactional” in the issue queue. Note that this can lead toover-marking if speculative loads are executed, for example on amispredicted branch path. The alternative of setting the TX-read 248 bitat load completion time was too expensive for silicon area, sincemultiple loads can complete at the same time, requiring many read-portson the load-queue.

Stores execute the same way as in non-transactional mode, but atransaction mark is placed in the store queue (STQ) 260 entry of thestore instruction. At write-back time, when the data from the STQ 260 iswritten into the L1 240, the TX-dirty bit 252 in the L1-directory 256 isset for the written cache line. Store write-back into the L1 240 occursonly after the store instruction has completed, and at most one store iswritten back per cycle. Before completion and write-back, loads canaccess the data from the STQ 260 by means of store-forwarding; afterwrite-back, the CPU 114 (FIG. 2) can access the speculatively updateddata in the L1 240. If the transaction ends successfully, the TX-dirtybits 252 of all cache-lines are cleared, and also the TX-marks of notyet written stores are cleared in the STQ 260, effectively turning thepending stores into normal stores.

On a transaction abort, all pending transactional stores are invalidatedfrom the STQ 260, even those already completed. All cache lines thatwere modified by the transaction in the L1 240, that is, have theTX-dirty bit 252 on, have their valid bits turned off, effectivelyremoving them from the L1 240 cache instantaneously.

The architecture requires that before completing a new instruction, theisolation of the transaction read- and write-set is maintained. Thisisolation is ensured by stalling instruction completion at appropriatetimes when XIs are pending; speculative out-of order execution isallowed, optimistically assuming that the pending XIs are to differentaddresses and not actually cause a transaction conflict. This designfits very naturally with the XI-vs-completion interlocks that areimplemented on prior systems to ensure the strong memory ordering thatthe architecture requires.

When the L1 240 receives an XI, L1 240 accesses the directory to checkvalidity of the XI′ed address in the L1 240, and if the TX-read bit 248is active on the XI′ed line and the XI is not rejected, the LSU 280triggers an abort. When a cache line with active TX-read bit 248 isLRU′ed from the L1 240, a special LRU-extension vector remembers foreach of the 64 rows of the L1 240 that a TX-read line existed on thatrow. Since no precise address tracking exists for the LRU extensions,any non-rejected XI that hits a valid extension row the LSU 280 triggersan abort. Providing the LRU-extension effectively increases the readfootprint capability from the L1-size to the L2-size and associativity,provided no conflicts with other CPUs 114 (FIGS. 1 and 2) against thenon-precise LRU-extension tracking causes aborts.

The store footprint is limited by the store cache size (the store cacheis discussed in more detail below) and thus implicitly by the L2 268size and associativity. No LRU-extension action needs to be performedwhen a TX-dirty 252 cache line is LRU′ed from the L1 240.

Store Cache

In prior systems, since the L1 240 and L2 268 are store-through caches,every store instruction causes an L3 272 store access; with now 6 coresper L3 272 and further improved performance of each core, the store ratefor the L3 272 (and to a lesser extent for the L2 268) becomesproblematic for certain workloads. In order to avoid store queuingdelays, a gathering store cache 264 had to be added, that combinesstores to neighboring addresses before sending them to the L3 272.

For transactional memory performance, it is acceptable to invalidateevery TX-dirty 252 cache line from the L1 240 on transaction aborts,because the L2 268 cache is very close (7 cycles L1 240 miss penalty) tobring back the clean lines. However, it would be unacceptable forperformance (and silicon area for tracking) to have transactional storeswrite the L2 268 before the transaction ends and then invalidate alldirty L2 268 cache lines on abort (or even worse on the shared L3 272).

The two problems of store bandwidth and transactional memory storehandling can both be addressed with the gathering store cache 264. Thecache 264 is a circular queue of 64 entries, each entry holding 128bytes of data with byte-precise valid bits. In non-transactionaloperation, when a store is received from the LSU 280, the store cache264 checks whether an entry exists for the same address, and if sogathers the new store into the existing entry. If no entry exists, a newentry is written into the queue, and if the number of free entries fallsunder a threshold, the oldest entries are written back to the L2 268 andL3 272 caches.

When a new outermost transaction begins, all existing entries in thestore cache are marked closed so that no new stores can be gathered intothem, and eviction of those entries to L2 268 and L3 272 is started.From that point on, the transactional stores coming out of the LSU 280STQ 260 allocate new entries, or gather into existing transactionalentries. The write-back of those stores into L2 268 and L3 272 isblocked, until the transaction ends successfully; at that pointsubsequent (post-transaction) stores can continue to gather intoexisting entries, until the next transaction closes those entries again.

The store cache 264 is queried on every exclusive or demote XI, andcauses an XI reject if the XI compares to any active entry. If the coreis not completing further instructions while continuously rejecting XIs,the transaction is aborted at a certain threshold to avoid hangs.

The LSU 280 requests a transaction abort when the store cache 264overflows. The LSU 280 detects this condition when it tries to send anew store that cannot merge into an existing entry, and the entire storecache 264 is filled with stores from the current transaction. The storecache 264 is managed as a subset of the L2 268: while transactionallydirty lines can be evicted from the L1 240, they have to stay residentin the L2 268 throughout the transaction. The maximum store footprint isthus limited to the store cache size of 64×128 bytes, and it is alsolimited by the associativity of the L2 268. Since the L2 268 is 8-wayassociative and has 512 rows, it is typically large enough to not causetransaction aborts.

If a transaction aborts, the store cache 264 is notified and all entriesholding transactional data are invalidated. The store cache 264 also hasa mark per doubleword (8 bytes) whether the entry was written by a NTSTGinstruction—those doublewords stay valid across transaction aborts.

Millicode-Implemented Functions

Traditionally, IBM mainframe server processors contain a layer offirmware called millicode which performs complex functions like certainCISC instruction executions, interruption handling, systemsynchronization, and RAS. Millicode includes machine dependentinstructions as well as instructions of the instruction set architecture(ISA) that are fetched and executed from memory similarly toinstructions of application programs and the operating system (OS).Firmware resides in a restricted area of main memory that customerprograms cannot access. When hardware detects a situation that needs toinvoke millicode, the instruction fetching unit 204 switches into“millicode mode” and starts fetching at the appropriate location in themillicode memory area. Millicode may be fetched and executed in the sameway as instructions of the instruction set architecture (ISA), and mayinclude ISA instructions.

For transactional memory, millicode is involved in various complexsituations. Every transaction abort invokes a dedicated millicodesub-routine to perform the necessary abort steps. The transaction-abortmillicode starts by reading special-purpose registers (SPRs) holding thehardware internal abort reason, potential exception reasons, and theaborted instruction address, which millicode then uses to store a TDB ifone is specified. The TBEGIN instruction text is loaded from an SPR toobtain the GR-save-mask, which is needed for millicode to know which GRs238 to restore.

The CPU 114 (FIG. 2) supports a special millicode-only instruction toread out the backup-GRs 224 and copy them into the main GRs 228. TheTBEGIN instruction address is also loaded from an SPR to set the newinstruction address in the PSW to continue execution after the TBEGINonce the millicode abort sub-routine finishes. That PSW may later besaved as program-old PSW in case the abort is caused by a non-filteredprogram interruption.

The TABORT instruction may be millicode implemented; when the IDU 208decodes TABORT, it instructs the instruction fetch unit to branch intoTABORT's millicode, from which millicode branches into the common abortsub-routine.

The Extract Transaction Nesting Depth (ETND) instruction may also bemillicoded, since it is not performance critical; millicode loads thecurrent nesting depth out of a special hardware register and places itinto a GR 228. The PPA instruction is millicoded; it performs theoptimal delay based on the current abort count provided by software asan operand to PPA, and also based on other hardware internal state.

For constrained transactions, millicode may keep track of the number ofaborts. The counter is reset to 0 on successful TEND completion, or ifan interruption into the OS occurs (since it is not known if or when theOS will return to the program). Depending on the current abort count,millicode can invoke certain mechanisms to improve the chance of successfor the subsequent transaction retry. The mechanisms involve, forexample, successively increasing random delays between retries, andreducing the amount of speculative execution to avoid encounteringaborts caused by speculative accesses to data that the transaction isnot actually using. As a last resort, millicode can broadcast to otherCPUs 114 (FIG. 2) to stop all conflicting work, retry the localtransaction, before releasing the other CPUs 114 to continue normalprocessing. Multiple CPUs 114 must be coordinated to not causedeadlocks, so some serialization between millicode instances ondifferent CPUs 114 is required.

Transactional memory systems may ease multi-threaded programming byguaranteeing that some dynamic code sequences (hereafter“transactions”), execute atomically and in isolation. Transactionalexecution addresses the need for scalable synchronization in computersoftware applications as more CPUs are used by those applications. Thecomputer software applications may additionally need to address thedetection and handling of transient erroneous execution failures(hereinafter “transient failures”), an issue critical to correctexecution. Transient failures may, for example, change logic values in acircuit due to the presence of charged particles in the environment andit may be critical for computer software applications to identify whenthis has occurred. Typically, mechanisms that detect and addresstransient failures may be expensive in terms of at least one ofcomplexity, design resources, and testing.

Thus, in computer software applications, especially criticalapplications, it may be desirable to use design capabilities fortransactional execution supporting correct execution to additionallyknow that the transaction executed correctly with respect to theoccurrence of transient failures, i.e., those failures due to transientstate changes induced, for example by charged particles. SuccessfullyCOMMITted transactions, while they may signal no ABORT conditionsoccurred for the transaction, may not indicate the transaction was freefrom transient failures. As more and more functionality is stored on ahardware chip, the likelihood of a radiation induced transient failureincreases. Transient failures may cause the data manipulated within thetransaction to be corrupted. Recognizing and handling transient failuresallows computer software applications to be more resilient.

Reliable computing ensures correct execution, free of transient errors.Typically, correct execution in conjunction with transactional executionhas required multiple executions of a transaction to run in parallel andin lockstep, as well as dedicated hardware to perform cycle-by-cyclecomparison of parallel execution results in order to detect transientfailures. Cycle-by-cycle comparisons may require a reference transactionand a compare transaction to run simultaneously. The cycles on thesystems on which the reference transaction and compare transaction runmust behave similarly and the computer system which runs the referencetransaction must have the ability to suppress state changes in thereference transaction. Transactional execution results comparison mayrequire the storing of large amounts of comparison data.

In embodiments of the disclosure, transient failures may be detected byexecuting the same transaction multiple times, either on the sameprocessor 114 (FIG. 16) consecutively or on multiple processors 114(FIG. 16) in parallel, without cycle-by-cycle comparisons and withoutcomparisons of large amounts of execution results. In an embodiment ofthe disclosure, this is achieved by generating and comparing atransactional execution digest (hereinafter “digest”). The digest may bea data structure representing a summarization of an unbounded number ofelements in a bounded representation. A robust digest may be generatedusing invariant data within the transaction and using an algorithmincluding, but not limited to, a HASH of the data values, a checksum,and an error-correcting code technique where differing data wouldgenerate differing digests. The digest may be a fixed length or avariable length and may summarize an entire transactional execution or asubset of the transactional execution. The digest generated by atransaction will be exactly replicable for each error-free execution ofthe transaction. Embodiments may utilize any number of “digest computingalgorithms” that are either currently known or may be invented in thefuture.

A “computed digest” may be the digest generated and updated within atransactional region, prior to saving the digest to a permanentlocation. The computed digest may reside, for example, in a storebuffer, a cache, or a software array. Once saved, the computed digestmay be used as a reference digest (hereinafter “reliability digest”)against which the processor 114 (FIG. 16) may compare to determinewhether a transaction executed correctly. The reliability digest may besaved to a location including, but not limited to, a transaction controlstructure, a processor defined location, a defined register, a controlregister, a special purpose register, a memory location not used by acomputer software application or a memory location supplied by thecomputer software application.

A “reliability-digest-generating transaction” may generate a computeddigest that may be saved as the reliability digest. A“reliability-digest-checking transaction” may generate a computed digestthat may be compared with the reliability digest. It should be noted,the reliability-digest-generating transaction and thereliability-digest-checking transaction should each use the sameinvariant data within the transaction and the same algorithm to generatethe digests in order to yield equivalent digests.

In reliable computing using a digest, not all successful transactionsCOMMIT their results, and even a non-COMMITting version of a transactionmay need to maintain a transactional write-set for the duration of thetransaction. The transactional write-set may allow the non-COMMITtingtransaction to generate a digest equivalent to a COMMITting version ofthe same transaction, when both transactions execute error-free. Thelocation in which the transactional write-set may reside includes, butis not limited to, a store buffer, a cache, and a software array.

Because the computed digest and the reliability digest should beequivalent for all error-free executions of a transaction, the processor114 (FIG. 16) or a computer software application may compare reliabilitydigests to one another or to a computed digest in order to detect andrecover from transient failures and single event failures. Comparingdigests may also allow the processor 114 (FIG. 16) or computer softwareapplication to detect and recover from permanent execution failuresincluding, but not limited to, failures in a single execution unit andmanufacturing defects in a single execution unit where there may bealternate execution units on which to execute. An execution unit mayinclude, but is not limited to, a core, a thread, and a processor. Thus,when one execution of a transaction uses an execution unit exhibiting apermanent execution failure, and another execution of the transactionuses an execution unit not exhibiting the same permanent executionfailure, a digest mismatch may occur. The digest mismatch may indicatean error condition during execution. In at least one embodiment of thedisclosure, a hardware or software scheduling component including, butnot limited to an instruction scheduler and a thread scheduler, may aimto increase the likelihood of executing on different hardware componentsto the extent practical subject to other system constraints including,but not limited to, performance, power, scheduling classes,partitioning, gang scheduling and user-provided scheduling instructions.Executing on different hardware components may ensure multi-executionusing a different set of execution units in order to detect permanentexecution failures.

The processor 114 (FIG. 16) may utilize the computed digests and thereliability digests to determine if a transaction executed correctly.The processor 114 (FIG. 16) may make the determination either within asingle execution of the transaction or across multiple executions,without depending on cycle-by-cycle comparisons, simultaneous executionor special abilities of the underlying systems. The processor 114 (FIG.16) may also utilize the computed digest to roll back the transactionand undo any changes when the transaction executes incorrectly.Transactions, hereinafter “reliable-execution transactions”, may bothgenerate and compare digests to ensure the transaction executedcorrectly.

A computer software application may run critical segments of code as areliable-execution transaction. Upon successful completion of thetransaction, the computer software application may reliably utilize anycalculations or other tasks accomplished in the transaction. Anunsuccessful return from the reliable-execution transaction may becaused, for example, by an ABORT due to conflicts, lack of buffer spaceor any of the traditional reasons for an ABORT, or may be caused by anexecution error due, for example, to a transient failure or a permanenterror on a hardware execution unit. The computer software applicationmay respond to a failure by, for example, retrying the transaction,retrying the transaction on a different execution unit or runningalternate code depending on the failure and the needs of theapplication.

The computer system 1600 (FIG. 16) may be configured such thatreliable-execution transactions may run and error conditions may beresolved without computer software application modification. Thecomputer system 1600 (FIG. 16) may, additionally, be configured torecognize and automatically remove continually failing execution unitsthat may be recognized during a reliable-execution transaction. Forthose computer software applications that may receive these errors, thecomputer software application may contain alternate code to handle anABORT condition, for example, by breaking the transaction into smallerexecution sections, running the transaction unprotected or obtaining asoftware lock. The computer software application may additionallycontain code to handle a permanent execution unit failure, for example,by running the transaction on an alternate core or thread (hereinafter“processor”). A computer software application may be required to saveand restore registers around a reliable-execution transaction and mayneed to be aware of any registers used by the reliable-executiontransaction to contain or address the reliability digest and any returndata.

Now referring to FIG. 4, flowchart 300 illustrates steps performed bythe processor 114 (FIG. 16) for ensuring the correct execution of atransaction during a reliable-execution transaction, within the dataprocessing environment of FIG. 16. The steps of the flowchart 300illustrate an embodiment of the disclosure in which thereliable-execution transaction may be run twice, in sequence, once as areliability-digest-generating version of the transaction followed by areliability-digest-checking version of the same transaction. Theprocessor 114 (FIG. 16) may identify a reliable-execution transaction bya reliable-execution transaction begin instruction, discussed in detailbelow, with reference to FIGS. 8, 10 and 12, or may automatically runthe transaction as a reliable-execution transaction in a systemconfigured to run reliable transactions. The processor 114 (FIG. 16), at310, may clear the computed digest in preparation for thereliable-execution transaction, and indicate which version of thetransaction is executing. The first executed transaction may be thereliability-digest-generating transaction; the second executedtransaction may be the reliability-digest-checking transaction. Theprocessor 114 (FIG. 16) may save the initial machine state, at 320. Foreach instruction in the reliable-execution transactional region, theprocessor 114 (FIG. 16) may, at 330, update the computed digest andupdate the diagnostic data. The processor 114 (FIG. 16) may iterate, at335, through each instruction in the reliable-execution transactionupdating the computed digest, as necessary, until the processor 114(FIG. 16) identifies a reliable-execution transaction end instruction,discussed in detail below, with reference to FIGS. 9, 11 and 13, oridentifies a traditional transaction end instruction for a processor 114(FIG. 16) configured to automatically run reliable transactions. If theprocessor 114 (FIG. 16) encounters a transaction suspend duringtransactional execution, the updating of the computed digest may besuspended as well. If the processor 114 (FIG. 16) encounters atransaction failure in a nested transaction, the processor 114 (FIG. 16)may roll back the computed digest to reflect the computed digest as itwas just prior to the start of the nested transaction. In anotherembodiment, where flattened nesting is implemented, when a nestedtransaction fails, rollback occurs to the outermost transaction, and thecomputed digest is cleared. Nested transaction will be discussed in moredetail below with reference to FIG. 15.

The processor 114 (FIG. 16), at 340, may determine if the transactioncompleted successfully. For an unsuccessful completion (ABORT) of eitherthe reliability-digest-generating version of the transaction or thereliability-digest-checking version of the transaction, at 340, theprocessor 114 (FIG. 16) may set a return value, at 380, to indicate tothe computer software application that the transaction may haveincorrectly executed due to the transaction ABORT. The return value maybe stored to the location passed (either explicitly or implicitly) asinput to the reliable-execution transaction or to the location definedby the computer system 1600 (FIG. 16) configured to automatically runtransactions reliably. The processor 114 (FIG. 16) may providediagnostic data, at 385, including but not limited to, the computeddigest, information detailing reasons the transaction aborted and theaddress that caused the abort, as well as the return value to thecomputer software application. Reasons a transaction aborts include, butare not limited to, interference from another transaction, interferencefrom another memory operation, and running out of resources. Theprocessor 114 (FIG. 16) may roll back any written memory data, at 390,and may also restore the initial machine state, at 395. In an embodimentin which the reliable-execution transaction is a constrainedtransaction, the processor 114 (FIG. 16) may restart the transactionautomatically.

For a successful (non-ABORT) completion of the reliable-executiontransaction, at 340, the processor 114 (FIG. 16) may determine, at 345,which version of the transaction completed successfully (non-ABORT). Fora successfully completed reliability-digest-generating version of thetransaction, the processor 114 (FIG. 16) may, at 350, save the computeddigest. The saved computed digest is the reliability digest. Thereliability digest may be used as the reference digest areliability-digest-checking version of the transaction compares itscomputed digest with to determine a successful execution (non-transientfailure) of the transaction. The reliability digest may be saved to thelocation passed (either explicitly or implicitly) as input to thereliable-execution transaction or to the location defined by thecomputer system 1600 (FIG. 16) configured to automatically run reliabletransactions. The reliability-digest-generating version of thetransaction may not COMMIT any computational results, but may only savethe reliability digest. Preferably, this embodiment may be used inconjunction with a reliability-digest-checking version of thetransaction which may compare its computed digest with the providedreliability digest, and may COMMIT the results when the digests match.

In another embodiment of the disclosure, thereliability-digest-generating version of the transaction may not COMMITany memory write results of the transaction and may save the reliabilitydigest but may additionally modify the register state. Preferably, thisembodiment may be used in conjunction with a reliability-digest-checkingversion of the transaction which may compare its computed digest withthe provided reliability digest, and may COMMIT the results when thedigests match. In this embodiment, it may be the responsibility of thecomputer software application executing on the processor 114 (FIG. 16)to capture and restore any register state that needs to be preservedacross the reliable-execution transaction.

In another embodiment of the disclosure, thereliability-digest-generating transaction my COMMIT the results of thetransaction in addition to saving a reliability digest.

Before re-executing the transaction as a reliability-digest-checkingversion of the transaction, the processor 114 (FIG. 16) may, at 355,roll back any memory data written by the reliability-digest-generatingversion of the transaction and may, at 360, restore the initial state ofthe machine with the exception of any register that may contain or pointto the saved reliability digest. The reliability-digest-checking versionof the transaction must execute under the same machine state and dataenvironment as the reliability-digest-generating version and thecomputed digest updates must exactly mirror the updates made by thereliability-digest-generating version of the transaction in order togenerate a digest that will yield an accurate indication whether thereliable-execution transaction executed correctly.

For a successfully completed (non-ABORT) reliability-digest-checkingversion of the transaction, determined at 345, the processor 114 (FIG.16) may obtain the reliability digest saved by thereliability-digest-generating version of the transaction. Thereliability digest may be obtained from the location passed (eitherexplicitly or implicitly) as input to the reliable-execution transactionor from the location defined by the computer system 1600 (FIG. 16)configured to automatically run reliable transactions. To determine ifthe transaction executed correctly, the processor 114 (FIG. 16) may, at365, compare the computed digest with the obtained reliability digest.Equivalence between the computed digest and the reliability digest mayindicate a successfully executed transaction. The processor 114 (FIG.16) may COMMIT the transaction, at 370, for a successfully executedtransaction and may set a return value, at 375, to indicate to thecomputer software application that the reliable-execution transactioncompleted successfully and correctly. The return value may be stored tothe location passed (either explicitly or implicitly) as input to thereliable-execution transaction or to the location defined by thecomputer system 1600 (FIG. 16) configured to automatically runtransactions reliably. Differences between the computed digest and thereliability digest, at 365, may indicate an error during transactionalexecution. The processor 114 (FIG. 16) may set a return value, at 380,to indicate to the computer software application that the transactionencountered an execution error during transactional execution. Anexecution error condition may appear similar to an ABORT condition tothe computer software application. Both may roll-back the written dataand return indications of failure, but the computer softwareapplication's response may differ. A computer software application maychose to execute alternate code for an ABORT return value due tointerference from another transaction, but may choose to re-execute thetransaction on the same or an alternate processor for an execution errorreturn value indicating a possible transient failure or permanenthardware failure. In an alternate embodiment, the computer softwareapplication may choose to simply restart the transaction with anexpectation that a transient failure may not recur. The return value maybe stored to the location passed (either explicitly or implicitly) asinput to the reliable-execution transaction or to the location definedby the computer system 1600 (FIG. 16) configured to automatically runreliable transactions. The processor 114 (FIG. 16) may additionally, at385, return diagnostic data to the computer software applicationincluding, but not limited to, the computed digest, informationdetailing reasons the execution failed, information detailing reasonsthe transaction ABORTed, the address that caused the ABORT, theinstruction that caused the execution failure, a list of transactionalexecution memory updates, a list of transactional execution memoryaddresses and a list of transactional execution instructions that wereincluded in the computed digest. The processor 114 (FIG. 16) may rollback any written memory data, at 390, and restore the initial machinestate, at 395. In an embodiment in which the reliable-executiontransaction is a constrained transaction, the processor 114 (FIG. 16)may restart the transaction automatically.

It should be noted that a digest mis-compare may be due to a number ofcauses, including, but not limited to, a change of data accessed by thetransaction between a first execution as a reliability-digest-generatingtransaction and a re-execution as a reliability-digest-checkingtransaction, a transient failure in at least one of the first or secondsuch transactions, and execution of one or more instructions of eitherexecution of the transaction on a permanently faulty execution unit,when the corresponding instruction of the other transaction is executedon an alternate, non-permanently faulty unit.

In one embodiment of the disclosure, a scheduling component including,but not limited to, an instruction, thread, process, partition andvirtual machine scheduler, may attempt to increase the likelihood ofdetecting permanently faulty units. The scheduling component may, forexample, ensure that corresponding instructions of thereliability-digest-generating transaction and thereliability-digest-checking transaction execute on different executionunits. Alternately, the scheduling component may increase the likelihoodthat the complementary transactions will be executed on differentexecution units by, for example, randomizing an assignment ofinstructions to execution units, threads, or processors. It should benoted that not all permanent failures may be detected. Exemplarypermanent failures that my not be detected include, but are not limitedto, corresponding instructions of the complementary transactions beingexecuted on the same faulty unit and a same permanent failure exhibitssimultaneously on multiple execution units.

In another embodiment, an execution error may cause the processor 114(FIG. 16) to restart the reliable-execution transaction in hopes of acorrect execution when restarted. For a transient failure, restartingthe transaction may result in a successful execution. The processor 114(FIG. 16) may continue to restart the failed reliable-executiontransaction until a threshold number of unsuccessful attempts have beenmade before returning an error result to the computer softwareapplication.

In embodiments, the method 300 of FIG. 4 may be implemented in software,hardware or a hybrid of hardware and software.

In one embodiment, a software transactional memory (STM) system mayperform the steps of method 300 in software. In one optimizedembodiment, there may be hardware support for computing digests whileother transactional memory steps are performed in software or a hybridof hardware and software in accordance with an STM implementation.Hardware support for computing digests may include, but is not limitedto, explicit digest instructions for indicated instructions (e.g., allor a subset of memory instructions), explicit digest instructions for astatically defined subset of all instructions (e.g., all memoryinstructions) and digest computing optionally subject to a mode enablingand disabling digest generation,

In another embodiment, all, or substantially all, of flowchart 300 maybe implemented directly in hardware. In one hardware embodiment,reliable-transaction boundaries may be indicated and hardware mayexecute such transactions twice, once as a reliability-digest-generatingtransaction and a second time as a reliability-digest-checkingtransaction. Restart for a reliability-digest-generating transactionalexecution and a reliability-digest-checking transactional execution maybe performed automatically in hardware. In at least one embodiment, thehardware may additionally implement retry policies when a mis-compare ofthe digests may be encountered. In one optimized embodiment, retrypolicies may be responsive to user parameters, including, but notlimited to, execution retry counts for a mis-compare of the digests.

In a hybrid hardware software embodiment, hardware support forreliability-digest-generating, reliability-digest-checking, andreliable-execution transactions may be provided. In one hybridembodiment, the hardware support for the reliability-digest-generating,reliability-digest-checking, and reliable-execution transactions mayinclude, but is not limited to, instructions to initiate transactionsfor reliability-digest-generation, reliability-digest-checking, andreliable-execution, respectively, as discussed below with reference toFIGS. 8-13. This hybrid embodiment may control flow and policy decisionsin software. The software may, for example control one or more aspectsof executing transactional code for reliability-digest-generation andreliability-digest-checking and may, for example, control policydecisions about whether to restart a transaction when a mis-compare ofthe digests may be detected.

In at least one embodiment, a reliability-digest-generating transactionand a corresponding reliability-digest-checking transaction may executein parallel to accelerate execution time. Advantageously, embodiments donot require parallel reliability-digest-generating transactions andcorresponding reliability-digest-checking transactions to run inlockstep, or on specific cores reflecting a presence of lockstepverification hardware.

Referring now to FIG. 5 and FIG. 6, schematic block diagramsillustrating embodiments in which the versions of the reliable-executiontransaction 500 and 600 run in parallel, on different processors 114 a,114 b (FIG. 1), within the data processing environment of FIG. 16. In anembodiment of the disclosure, one processor 114 a (FIG. 1) may executethe reliability-digest-generating version 500 of the transaction,another, the reliability-digest-checking version 600 of the sametransaction. Each complimentary version of the reliable-executiontransaction may begin with the same initial transaction state, and eachmay execute with their own transaction write-set of uncommitted dataupdates in order to generate equivalent digests using identical data. Ina computer system 1600 (FIG. 16) configured to run reliabletransactions, the computer system 1600 (FIG. 16) may establish anenvironment where data conflicts between the two complimentary versionsof the reliable-execution transaction running simultaneously may beignored. Ignoring conflicts between complimentary versions of thereliable-execution transactions may avoid the introduction of falseconflicts that may arise from the reliability-digest-generatingtransaction and the reliability-digest-checking transaction operating onthe same data. The reliability-digest-generating version 500 of thetransaction may never COMMIT the data changes to memory so all datawrites may appear as uncommitted data to its compliment. In anembodiment of the disclosure, a token may be sent with a data update andpassed between processors 114 a, 114 b (FIG. 1) to identify the dataupdate of the complementary versions 500 and 600 of the transaction. Inanother embodiment, the token sent with the data update for thereliability-digest-generating version 500 of the transaction may signalto all other transactions that the data may never be COMMITted to memoryand may never cause a conflict.

When the reliable-execution transaction versions are run on multipleprocessors 114 (FIG. 16), the complimentary versions of the transactionmay need to synchronize and communicate to verify the transactionexecuted correctly. Complementary versions 500 and 600 of thereliable-execution transaction running on different processors 114 (FIG.16) may not have access to each others' registers, cache, or processordefined locations and may need alternate methods to pass the reliabilitydigest. In addition, since instructions within the transactional regionmay execute in an order different than the order fetched and since thereliability-digest-checking version 600 of the reliable-executiontransaction may reach its TXEND instruction before thereliability-digest-generating version 500 has saved the reliabilitydigest, the complementary versions 500 and 600 may need to identify eachother and synchronize their executions. Thereliability-digest-generating version 500 of the transaction may not beconsidered complete until the transaction ABORTs or the reliabilitydigest is saved. The reliability-digest-checking version 600 of thetransaction may not be considered complete until the transaction COMMITsor ABORTs.

With continued reference to FIG. 5, illustrating an embodiment of thedisclosure in which the complementary versions of the reliable-executiontransaction 500 and 600 may run on different processors 114 a, 114 b(FIG. 1), and in which each may access a shared synchronization block520. The shared synchronization block 520 may be initialized at thebeginning of the reliable-execution transaction such that the twocomplementary versions 500 and 600 of the transaction may identify eachother. The shared synchronization block 520 may additionally include thereliability digest 550 or an address of a location where the reliabilitydigest 550 may be stored or obtained. Once thereliability-digest-generating version 500 of the reliable-executiontransaction has saved the reliability digest 550, it may be available tothe reliability-digest-checking version 600 of the reliable-executiontransaction. The reliability-digest-checking version 600 may need towait and re-sample the synchronization block 520 when an attempt toobtain the reliability digest 550 occurs before thereliability-digest-generating version 500 has saved it. Alternately, thecomputer system 1600 (FIG. 16) may be configured to notify thereliability-digest-checking version 600 when thereliability-digest-generating version 500 saves the reliability digest550. The synchronization block 520 may include additional transactioninformation including, but not limited to, success indicators for eachof the complementary versions 500 and 600 of the reliable-executiontransaction, completion indicators and ID tokens for the transaction.

With continued reference to FIG. 6, illustrating an embodiment of thedisclosure in which the complementary versions of the reliable-executiontransaction 500 and 600 may run on different processors 114 a, 114 b(FIG. 1), and in which each may be identified by a shared ID, and inwhich each may communicate through a Digest Broadcast Bus 650. TheDigest Broadcast Bus 650 may be a hardware bus accessible from eachprocessor 114 a, 114 b (FIG. 1). The shared ID may be initialized at thebeginning of the reliable-execution transaction such that the twocomplementary versions 500 and 600 of the transaction may identify eachother. The ID may be hardware generated or software generated. Any datawritten by the complementary versions 500 and 600 of thereliable-execution transaction may be identified with the shared IDinitialized at the beginning of the transaction. Data conflicts may beignored for any data identified with a complimentary ID. Data conflictswith a different ID or data conflicts with no ID may cause thetransaction to ABORT. Once a reliability-digest-generating version 500of the reliable-execution transaction has completed, the generatedreliability digest identified with the shared ID 680 may be broadcastacross the Digest Broadcast Bus 650. As discussed above, with referenceto FIG. 5, the reliability-digest-checking version 600 may need to waitfor the reliability digest identified with the shared ID 680 to be savedand, in this embodiment, broadcast. The computer system 1600 (FIG. 16)may also be configured to notify the reliability-digest-checking version600 when the reliability digest identified with the shared ID 680 hasbeen broadcast. The Digest Broadcast Bus 650 may broadcast additionaltransaction information including, but not limited to, successindicators for each of the complimentary versions 500 and 600 of thereliable-execution transaction and completion indicators, eachidentified with the shared ID of the reliable-execution transaction.

In at least one embodiment of FIGS. 5 and 6, within the data processingenvironment of FIG. 16, the reliability-digest-generating transactionand the reliability-digest-checking transaction may be dynamicallyidentified. In one embodiment, the first of the transactions 500, 600 tocomplete may become the reliability-digest-generating transaction bysaving a digest and rolling back its memory state. The secondtransaction to complete may become the reliability-digest-checkingtransaction. Because the operations of the reliability-digest-generatingand reliability-digest-checking transactions may be symmetric until step345 (FIG. 4), the processor 114 a, 114 b (FIG. 1) may, with minimalincremental overhead, differentiate, at 345 (FIG. 4) to allow the firsttransaction to substantially de-allocate most of the resourcesassociated with the transactional execution.

As discussed above, embodiments may utilize any number of “digestcomputing algorithms” that are either currently known or may be inventedin the future.

In one embodiment of the disclosure, the processor 114 (FIG. 16) mayHASH only written memory to update the computed digest. Speculativeexecution, common in many processors today, may affect the generation ofthe computed digest. Only updating the computed digest for memory writeinstructions may generate the computed digest with the least likelihoodof requiring a roll back due to mis-speculation. Computer system 1600(FIG. 16) may track write instructions more aggressively than otherinstruction types and speculatively written data may be invalidated bythe computer system 1600 (FIG. 16) when mis-speculation occurs.Speculatively read data may not be tracked by computer system 1600 (FIG.16), thereby requiring additional support to roll back speculativelyread data from the computed digest. Two transactions with the same writeset may have the same user-visible effect and may, therefore, generateidentical digests.

Some processors 114 (FIG. 16) may only write the data to memory when theinstruction has completed successfully. In this environment, theprocessor 114 (FIG. 16) may never need to roll back the updated computeddigest. Other processors 114 (FIG. 16) may write the data speculativelyto a store queue and back out any data from the store queue when aninstruction error is detected. The processor 114 (FIG. 16) may thenrestart the instruction execution. In this environment, the processor114 (FIG. 16) may need to roll back the memory write data from thecomputed digest as well.

In another embodiment of the disclosure, the processor 114 (FIG. 16) mayHASH memory data read during the transaction, in addition to the writtendata. The created read HASH values may be used to update the computeddigest. Updating the computed digest with the read values along with thewritten values may generate a more robust computed digest and morereliable computing. Speculative reads, if used to update the computeddigest, may be non-replicable since multiple executions of thetransaction may speculate the reads differently. The processor 114 (FIG.16), in this embodiment, may need to ensure the computed digest reflectsonly the read data that corresponds exactly with the execution of thetransaction and roll back any updates to the computed digest made forthe speculative reads.

In another embodiment, the processor 114 (FIG. 16) may additionallyupdate the computed digest with HASH values of General Purpose Registers(GPRs) updated during the execution of the transaction. It should benoted, this embodiment may also need to be aware of speculative GPRupdates. Like speculative reads above, speculative GPR updates may causethe resulting computed digest to be non-replicable due to multipleexecutions of the transaction speculating differently. The processor 114(FIG. 16), in this embodiment, may need to ensure the computed digestreflects only the data that corresponds exactly with the execution ofthe transaction and roll back any updates to the computed digest madefor speculative GPR updates.

In one or more embodiments, the GPR set may additionally include, but isnot limited to, floating point registers, vector registers, mediaregisters, vector-scalar registers, condition registers, conditionfields, predicate registers, special purpose registers, controlregisters, and machine-specific registers.

In another embodiment of the disclosure, the processor 114 (FIG. 16) mayadditionally update the computed digest with HASH values of data writtento external memory and other storage locations including, but notlimited to, on-chip registers. It should be noted, this embodiment mayneed to be aware that speculative branching, like speculative reads andGPR updates above, may cause the resulting digest to be non-replicabledue to multiple executions of the transaction speculating differently.The processor 114 (FIG. 16), in this embodiment, may need to ensure thecomputed digest reflects only the data that corresponds exactly with theexecution of the transaction and roll back any updates to the computeddigest made for data written to external memory during speculativebranching.

Rolling back updates to the computed digest due to mis-speculation maybe accomplished with a variety of methods. In one embodiment of thedisclosure, computed digest snapshots may be taken in conjunction withother snapshots including, but not limited to, register maps snapshotwhen performing register renaming, as described by Buti et al.

In another embodiment of the disclosure, the processor 114 (FIG. 16) mayupdate the computed digest with the HASH of the write-set during theexecution of the transaction, but may additionally update the computeddigest at the end of the transaction with a HASH created on a snapshotof the final GPR values. This may allow for a more robust computeddigest without adding additional roll back concerns.

In another embodiment, the computed digest may also be updated with amemory address to which data within the transaction was written. Thisembodiment may allow the processor 114 (FIG. 16) to determine aninstruction error occurred by detecting memory address differences whencomparing reliability and/or computed digests.

In another embodiment of the disclosure, the computed digest may begenerated at the end of the transaction rather than during thetransaction.

Now referring to FIG. 7, flowchart 700 illustrates steps performed bythe processor 114 (FIG. 16) for generating a computed digest at the endof a transactional execution, within the data processing environment ofFIG. 16. The steps of the flowchart 700 illustrate the generation of acomputed digest, in accordance with an embodiment of the disclosure. Inthis embodiment, the processor 114 (FIG. 16) may execute the transactionnormally, at 701, utilizing an in-memory log buffer. The in-memory logbuffer (hereafter “transaction buffer”) may be used by memory managementhardware to store all transactional data modifications during thetransaction. The processor 114 (FIG. 16) may iterate, at 705, until theentire transactional region has been executed and the transaction may beready to COMMIT. The processor 114 (FIG. 16) may, at 710, clear thecomputed digest and at 715 obtain the first of the transactional datamodifications stored in the transaction buffer. The processor 114 (FIG.16) may update the computed digest, at 720, with a HASH created for thedata modification obtained from the transaction buffer. The processor114 (FIG. 16) may, at 725, iterate through each transactional datamodification stored in the transaction buffer and when all thetransactional data modifications in the transaction buffer have beenadded to the computed digest, the processor 114 (FIG. 16) may continue,at 730, completing the transaction. This embodiment may eliminate theneed for roll back processing since the data has already beensuccessfully written or read before the computed digest is updated. Atransaction delay may result with this embodiment due to the serialprocessing of the transaction buffer after the completion of thetransaction execution.

Another embodiment of the disclosure, where the computed digest may begenerated at the end of the transaction, may update the computed digestwith a HASH created on a snapshot including, but not limited to, thefinal state of the memory written during the reliable-executiontransaction, the final state of the memory read during thereliable-execution transaction, and the final values of the GPRs. Theprocessor 114 (FIG. 16) may, in this embodiment, utilize the transactionbuffer to create the HASH of the data modifications, but in thisembodiment, only the final data values will be used to update thecomputed digest. As discussed above, this embodiment may eliminate theneed for roll back processing since the data has already beensuccessfully written or read before the computed digest is updated.Again, a transaction delay may result with this embodiment but the delaymay be lessened due to utilizing only final data values to update thecomputed digest.

Now referring to FIGS. 8-13 which illustrate exemplary instructions forsignaling the beginning of a reliability-digest-generating transaction,a reliability-digest-checking transaction and a reliable-executiontransaction, hereinafter “digest transaction”, and for signaling the endof the digest transaction, in accordance with an embodiment of thedisclosure. These examples and figures are illustrative rather thanlimiting.

FIGS. 8 and 9 illustrate examples of new transaction begin instructionsand a new transaction end instructions recognized within the computersystem 1600 (FIG. 16). A TXBEGIN.GEN (FIG. 8) instruction may signal tothe processor 114 (FIG. 16) to begin a reliability-digest-generatingtransaction. A TXBEGIN.COMP (FIG. 8) instruction may signal to theprocessor 114 (FIG. 16) to begin a reliability-digest-checkingtransaction. A TXBEGIN.REL (FIG. 8) instruction may signal to theprocessor 114 (FIG. 16) to begin a reliable-execution transaction.Collectively, the above exemplary instructions will be referred to asTXBEGIN.X when a description applies to all 3 instructions. A TXEND.GEN(FIG. 9) instruction may signal to the processor 114 (FIG. 16) to endthe reliability-digest-generating transaction. A TXEND.COMP (FIG. 9)instruction may signal to the processor 114 (FIG. 16) to end thereliability-digest-checking transaction. A TXEND.REL (FIG. 9)instruction may signal to the processor 114 (FIG. 16) to end thereliable-execution transaction. Collectively, the above exemplaryinstructions will be referred to as TXEND.X when a description appliesto all 3 instructions.

The TXBEGIN.X and the TXEND.X instructions may each include newoperation codes recognized by the computer system 1600 (FIG. 16). Thenew TXBEGIN.X instructions may signal to the processor 114 (FIG. 16)that a digest transaction may be beginning and that all subsequentinstructions until the associated TXEND.X instruction may be part of thetransactional region and may be utilized in computing the digest. Boththe TXBEGIN.X and the TXEND.X instructions may be specified with orwithout an input/output parameter 410, 420. The TXEND.COMP and theTXEND.REL instructions may be specified with or without an outputparameter 425. The input/output parameter 410, 420 may specify alocation used to save a generated reliability digest(TXBEGIN.GEN/TXEND.GEN, TXBEGIN.REL/TXEND.REL) or a location to obtain apreviously generated reliability digest (TXBEGIN.COMP/TXEND.COMP) andmay be specified on either the TXBEGIN.X instruction or on the TXEND.Xinstruction. The output parameter 425 on the TXEND.COMP and theTXEND.REL instructions may specify a location to return a result of thereliability-digest-checking transaction or the reliable-executiontransaction.

For a digest transaction in which neither the TXBEGIN.X instruction northe TXEND.X instruction includes the input/output parameter 410, 420,the generated reliability digest (TXBEGIN.GEN/TXEND.GEN,TXBEGIN.REL/TXEND.REL) may be saved to an implicit location defined bythe computer system 1600 (FIG. 16) or the previously generatedreliability digest (TXBEGIN.COMP/TXEND.COMP) may be obtained from animplicit location defined by the computer system 1600 (FIG. 16). For aTXEND.COMP or TXEND.REL instruction that does not include the outputparameter 425, the return value and diagnostic data for thereliability-digest-checking transaction or the reliable-executiontransaction may be placed in an implicit location defined by thecomputer system 1600 (FIG. 16). Implicit locations may be locations thatdo not interfere with computer software applications. Implicit locationsmay include, but are not limited to, a transaction control structure, aprocessor defined location, a defined register, a control register and aspecial purpose register. The implicit location may not be a part of thetransaction state.

For a digest transaction where either the TXBEGIN.X or the TXEND.Xinstruction includes an addr (address) input/output parameter 410, thegenerated reliability digest (TXBEGIN.GEN/TXEND.GEN,TXBEGIN.REL/TXEND.REL) may be saved to a memory location specified bythe addr parameter 410 or the previously generated reliability digest(TXBEGIN.COMP/TXEND.COMP) may be obtained from the memory locationspecified by the addr parameter 410.

For a digest transaction with either the TXBEGIN.X or the TXEND.Xinstruction including an Rx (register) input/output parameter 420 and areliability digest small enough to fit within a register, the generatedreliability digest (TXBEGIN.GEN/TXEND.GEN, TXBEGIN.REL/TXEND.REL) may besaved in the register specified by the Rx parameter 420 or thepreviously generated reliability digest (TXBEGIN.COMP/TXEND.COMP) may beobtained from the register specified by the Rx parameter 420. For adigest transaction with either the TXBEGIN.X or the TXEND.X instructionincluding an Rx register input/output parameter 420 and a reliabilitydigest larger than may fit within the register, the generatedreliability digest (TXBEGIN.GEN/TXEND.GEN, TXBEGIN.REL/TXEND.REL) may besaved to a memory location specified by the contents of the Rx registerparameter 420 or the previously generated reliability digest(TXBEGIN.COMP/TXEND.COMP) may be obtained from the memory locationspecified by the Rx parameter 420. The specified register may not bepart of the transaction state.

The TXEND.COMP and TXEND.REL instructions may additionally include an Rcoutput parameter 425 to return the results of comparing the reliabilitydigest with the computed digest. The output parameter 425, specified bythe computer software application, may include, but is not limited to, aregister, a memory location addressed by the contents of the register Rcand an address (addr) of a memory location. The output parameter 425 maybe set to a return value indicating a successful or failed equivalencecomparison between the digests compared, along with a diagnostic data. Avariety of other explicit or implicit locations for storing a digest maybe practiced in conjunction and within the scope of the disclosure,including, but not limited to, control registers, fixed memory locationsand memory locations in privileged memory.

FIGS. 10 and 11 illustrate examples of an existing transaction begininstruction and an existing transaction end instruction, recognizedwithin the computer system 1600 (FIG. 16), for which an immediateoperand 430 has been added. A TXBEGIN {0, 1, 2, 3} (FIG. 10) instructionmay signal the processor 114 (FIG. 16) to begin a digest transaction. ATXEND {0, 1, 2, 3} (FIG. 11) instruction may signal to the processor 114(FIG. 16) to end the digest transaction. The TXBEGIN {0, 1, 2, 3} andthe TXEND {0, 1, 2, 3} instructions may each include a new immediateoperand {0, 1, 2, 3} 430 recognized by the computer system 1600 (FIG.16). An immediate operand 430 of {0}, as exemplified in TXBEGIN 0, maysignal to the processor 114 (FIG. 16) to execute the transaction as atraditional, non-digest transaction. An immediate operand 430 of {1}, asexemplified in TXBEGIN 1, may signal to the processor 114 (FIG. 16) thata reliability-digest-generating transaction may be beginning and allsubsequent instructions until a TXEND 1 instruction may be part of thetransactional region and may be utilized in generating the reliabilitydigest. An immediate operand 430 of {2}, as exemplified in TXBEGIN 2,may signal to the processor 114 (FIG. 16) that areliability-digest-checking transaction may be beginning and allsubsequent instructions until a TXEND 2 instruction may be part of thetransactional region and may be utilized in checking the transactionalexecution. An immediate operand 430 of {3}, as exemplified in TXBEGIN 3,may signal to the processor 114 (FIG. 16) that a reliable-executiontransaction may be beginning and all subsequent instructions until aTXEND 3 instruction may be part of the transactional region and may beutilized in verifying the correctness of the transactional execution.Both the TXBEGIN {0, 1, 2, 3} and the TXEND {0, 1, 2, 3} instructionsmay be specified with or without an input/output parameter 410, 420 andthe TXEND {0, 1, 2, 3} with or without an output parameter 425. Theinput/output parameter 410, 420 may specify a location to save agenerated reliability digest (TXBEGIN {1, 3}/TXEND {1, 3}) or to obtaina previously generated reliability digest (TXBEGIN 2/TXEND 2) and may bespecified either on the TXBEGIN {0, 1, 2, 3} instruction or on the TXEND{0, 1, 2, 3} instruction. The output parameter 425 on the TXEND {0, 1,2, 3} instruction may specify a location to return a result of thedigest transaction. For a traditional, non-digest transaction, theparameters 410, 420, 425 may be ignored. For areliability-digest-generating transaction (TXBEGIN 1), the outputparameter 425 may be ignored.

For a digest transaction in which neither the TXBEGIN {1, 2, 3}instruction nor the TXEND {1, 2, 3} instruction includes theinput/output parameter 410, 420, the generated reliability digest(TXBEGIN {1, 3}/TXEND {1, 3}) may be saved to an implicit locationdefined by the computer system 1600 (FIG. 16) or the previouslygenerated reliability digest (TXBEGIN 2/TXEND 2) may be obtained from animplicit location defined by the computer system 1600 (FIG. 16). For aTXEND {2, 3} instruction that does not include the output parameter 425,the return value and diagnostic data for the reliability-digest-checkingtransaction or the reliable-execution transaction may be placed in animplicit location defined by the computer system 1600 (FIG. 16).Implicit locations may be locations that do not interfere with computersoftware applications. Implicit locations may include, but are notlimited to, a transaction control structure, a processor definedlocation, a defined register, a control register and a special purposeregister. The implicit location may not be a part of the transactionstate.

For a digest transaction in which either the TXBEGIN {1, 2, 3} or theTXEND {1, 2, 3} instruction includes an addr (address) input/outputparameter 410 or an Rx (register) input/output parameter 420, and for aTXEND {2, 3} instruction which includes an Rc output parameter 425, theparameters are handled as discussed above for FIGS. 8 and 9.

FIGS. 12 and 13 illustrate examples of an existing transaction begininstruction and an existing transaction end instruction, recognizedwithin the computer system 1600 (FIG. 16), for which a register operandhas been added. A TXBEGIN Ry (FIG. 12) instruction may signal theprocessor 114 (FIG. 16) to begin a digest transaction. A TXEND Ry (FIG.13) instruction may signal to the processor 114 (FIG. 16) to end thedigest transaction. The register operand 440, Ry, may contain anexemplary value of 0, 1, 2 or 3 recognized by the computer system 1600(FIG. 16). A register operand 440 of Ry=0, as exemplified in TXBEGIN Ry(Ry=0), may signal to the processor 114 (FIG. 16) to execute thetransaction as a traditional, non-digest transaction. A register operand440 of Ry=1, as exemplified in TXBEGIN Ry (Ry=1) may signal to theprocessor 114 (FIG. 16) that a reliability-digest-generating transactionmay be beginning and all subsequent instructions until a TXEND Ry (Ry=1)instruction may be part of the transactional region and may be utilizedin generating the reliability digest. A register operand 440 of Ry=2, asexemplified in TXBEGIN Ry (Ry=2), may signal to the processor 114 (FIG.16) that a reliability-digest-checking transaction may be beginning andall subsequent instructions until a TXEND Ry (Ry=2) instruction may bepart of the transactional region and may be utilized in checking thetransactional execution. A register operand 440 of Ry=3, as exemplifiedin TXBEGIN Ry (Ry=3), may signal to the processor 114 (FIG. 16) that areliable-execution transaction may be beginning and all subsequentinstructions until a TXEND Ry (Ry=3) instruction may be part of thetransactional region and may be utilized in verifying the correctness ofthe transactional execution. Both the TXBEGIN Ry and the TXEND Ryinstructions may be specified with or without an input/output parameter410, 420 and the TXEND Ry (FIG. 13) with or without an output parameter425. The input/output parameter 410, 420 may specify a location to savea generated reliability digest (TXBEGIN Ry/TXEND Ry (Ry={1, 3})) or toobtain a previously generated reliability digest (TXBEGIN Ry/TXEND Ry(Ry=2)) and may be specified either on the TXBEGIN Ry instruction or onthe TXEND Ry instruction. The output parameter 425 on the TXEND Ryinstruction may specify a location to return a result of the digesttransaction. For a traditional, non-digest transaction, the parameters410, 420, 425 may be ignored. For a reliability-digest-generatingtransaction (TXBEGIN Ry (Ry=1)), the output parameter 425 may beignored.

For a digest transaction in which neither the TXBEGIN Ry instruction northe TXEND Ry instruction includes the input/output parameter 410, 420,the generated reliability digest (TXBEGIN Ry/TXEND Ry (Ry={1, 3})) maybe saved to an implicit location defined by the computer system 1600(FIG. 16) or the previously generated reliability digest (TXBEGINRy/TXEND Ry (Ry=2)) may be obtained from an implicit location defined bythe computer system 1600 (FIG. 16). For a TXEND Ry (Ry={2, 3})instruction that does not include the output parameter 425, the returnvalue and diagnostic data for the reliability-digest-checkingtransaction or reliable-execution transaction may be placed in animplicit location defined by the computer system 1600 (FIG. 16).Implicit locations may be locations that do not interfere with computersoftware applications. Implicit locations may include, but are notlimited to, a transaction control structure, a processor definedlocation, a defined register, a control register and a special purposeregister. The implicit location may not be a part of the transactionstate.

For a digest transaction where either the TXBEGIN Ry (Ry={1, 2, 3}) orthe TXEND Ry (Ry={1, 2, 3}) instruction includes an addr (address)input/output parameter 410 or an Rx (register) input/output parameter420, and for a TXEND Ry (Ry={2, 3}) instruction which includes an Rcoutput parameter 425, the parameters are handled as discussed above forFIGS. 8 and 9.

Now referring to FIG. 14 which illustrates an exemplary instruction,DIGEST, for including specific data in the reliability digest or forstarting and ending reliability-digest-generation during thetransactional execution, in accordance with an embodiment of thedisclosure. This example and figure is illustrative rather thanlimiting.

FIG. 14 illustrates an example of a new DIGEST instruction, recognizedwithin the computer system 1600 (FIG. 16), which may allow a computersoftware application to instruct the processor 114 (FIG. 16) to updatethe reliability digest with computer software application specifieddata. The DIGEST instruction may include one or more reg (register)and/or addr (address) input parameters 450 a-450 z, 451 a-451 zspecifying data to include in the update of the computed digest. The oneor more registers include, but are not limited to, general registers,floating-point registers and control registers. The specified registersand/or addresses may be used to update the computed digest during theexecution of the digest transaction as they are modified or as asnapshot of their values at the end of the digest transaction.

In another embodiment, the DIGEST instruction may allow the computersoftware application to instruct the processor 114 (FIG. 16) to generatea computed digest within a traditional, non-digest transaction, upon theprocessor 114 (FIG. 16) recognizing a DIGEST instruction with a BEGINoperand 452. A DIGEST instruction with an END operand 453 may stop thegenerating of the computed digest. The DIGEST BEGIN and DIGEST ENDinstructions may include an input/output parameter 410, 420 as discussedabove with reference to FIGS. 8-13.

The following exemplary code segments illustrate embodiments of acomputer software application's addressing the detection and handling oftransient failures and permanent execution unit failures utilizingreliability-digest-generating transactions andreliability-digest-checking transactions in conjunction with theTXBEGIN.X and TXEND.X instructions described above with reference toFIGS. 8 and 9.

Table 5 represents an exemplary C code segment including inlinereliability-digest-generating and reliability-digest-checkingtransactions.

TABLE 5 C Code Example #define threshold 10 extern int a[ ], b[ ]; foo() { int digest; int fail; a[0] = 0; b[0] = 0; fail = 0; retry: asmvolatile (“txbegin.gen”     : /* no outputs */     : /* no inputs */    : /* clobber list */ “memory”); a[0] = a[0] +1; b[0] = a[0] +2; asmvolatile (“txend.gen %0”     : /* output digest */ “=r” (digest)     :/* no inputs */     : /* clobber list */ “memory” ); asm volatile(“txbegin.comp”    : /* no outputs */    : /* no intputs */    : /*clobber list */ “memory”); a[0] = a[0] +1; b[0] = a[0] +2; asm volatile(“txend.comp cr0, %0W; bne [failure]”     : /* no output */     : /*digest as input */ “r” (digest)     : /* clobber list */ “x”, “memory”    : /* label for failure processing */ failure); more_computation( );return; failure: fail ++; if (fail < threshold)     goto retry /* e.g.,log, terminate application, migrate, etc. */ advanced_failure_handling(); }

Table 6 represents an exemplary C code segment with language extensionsincluding reliability-digest-generating and reliability-digest-checkingtransactions. The compiler may translate the transaction instructionsinto machine operands understood by the computer system 1600 (FIG. 16)to begin or end a digest transaction.

TABLE 6 C Code With Language Extensions Example #define threshold 10extern int a[ ], b[ ]; foo( ) { int digest; int fail; a[0] = 0; b[0] =0; fail = 0; retry: transaction_begin_gendigest ; a[0] = a[0] +1; b[0] =a[0] +2; transaction_end_gendigest (digest);transaction_begin_comparedigest ; a[0] = a[0] +1; b[0] = a[0] +2;transaction_end_comparedigest(digest,failure) more_computation( );return; failure: fail ++; if (fail < threshold)     goto retry /* e.g.,log, terminate application, migrate, etc. */ advanced_failure_handling(); }

Table 7 represents an exemplary assembler code segment as it may begenerated by a compiler. This code sample demonstrates one of the risksof computer software application implementation of areliability-digest-generating transactions followed by areliability-digest-checking transaction where a compiler may generatedifferent assembler code for each of the complementary transactions.

TABLE 7 Generated Assembler Code Example L.foo: Id 10,.LC1@toc(2) ; baseaddress of a Id 9,.LC0@toc(2) ; base address of b mflr 0 li 11,10 std0,16(1) stdu 1,−112(1) li 0,0 mtctr 11 stw 0,0(10) stw 0,0(9) .L2:txbegin.gen lwz 11,0(9) addi 11,11,1 stw 11,0(9) addi 11,11,2 stw11,0(10) txend.gen 0 txbegin.comp lwz 11,0(9) addi 11,11,1 addi 8,11,2stw 11,0(9) stw 8,0(10) txend.comp cr0, 0 bne .L3 .L9: blmore_computation nop addi 1,1,112 Id 0,16(1) mtlr 0 blr .L3: bdnz L2 bladvanced_failure_handling nop addi 1,1,112 Id 0,16(1) mtlr 0 blr

In one embodiment of the disclosure, the compiler may receive a singlecopy of the transaction sequence and may replicate the codeautomatically in a manner adapted to reliably generate the same digest.In another embodiment, such a compiler also may also generate thereliability-digest-checking transaction code automatically, withoutcomputer software application interaction.

Table 8 is an exemplary code segment illustrating an embodiment of acomputer software application handling a transient failure or permanentexecution unit failures utilizing a reliable-execution transaction.

TABLE 8 Reliable-Execution Transaction Example extern int a[ ], b[ ];foo( ) { a[0] = 0; b[0] = 0; fail = 0; retry:reliable_transaction_begin; a[0] = a[0] +1; b[0] = a[0] +2;reliable_transaction_end; more_computation( ); return; }

In at least one such embodiment above, the recovery sequence may bestandardized and automatically generated by the compiler. In anotherembodiment, the computer software application provides additionalparameters, for example, a retry count and an error function to handletransactional execution failure, as illustrated in the exemplary codesegment in Table 9 below.

TABLE 9 Retry Count and Error Function Example extern int a[ ], b[ ];foo( ) { a[0] = 0; b[0] = 0; fail = 0; retry: reliable_transaction_begin(retry_count = 10, error_function ); a[0] = a[0] +1; b[0] = a[0] +2;reliable_transaction_end; more_computation( ); return; }

Transaction nesting may be used in conjunction with digest transactions.Digest transactions may be nested within both digest transactions andnon-digest transactions. Non-digest transaction may be nested withindigest transaction. Digest and non-digest transactions may be multiplynested. An inner-most computed digest may be combined progressivelyoutward with each previous nesting level transaction's computed digestuntil the final computed digest reflects the execution of all nestedtransactions.

In one embodiment of the disclosure, the computed digest may be updateddirectly, during the execution of a nested transaction. The processor114 (FIG. 16) may save a snapshot of the computed digest, as a nestinglevel snapshot of the computed digest, each time a nested transaction isstarted. The processor 114 (FIG. 16) may update the computed digestduring the execution of each nested transaction. Upon an unsuccessfulcompletion of one or more of the nested transactions, the processor 114(FIG. 16) may restore the computed digest from the unsuccessful nestedtransaction's nesting level snapshot of the computed digest.

In another embodiment, the computed digest may be updated only when allnested transactions have completed. The processor 114 (FIG. 16) maygenerate a new nesting level computed digest for each new nestedtransaction. The processor 114 (FIG. 16) may also save a snapshot of thecomputed digest, as a nesting level snapshot of the computed digest,each time a nested transaction is started. For the original non-nestedtransaction, the snapshot may reflect the computed digest; for a nestedtransaction, the snapshot may reflect the nesting level computed digest.As each nested transaction completes, the processor 114 (FIG. 16) mayreplace the previous nesting level transaction's nesting level computeddigest with a merge of the nested transaction's nesting level computeddigest and the nesting level snapshot of the computed digest saved priorto the nested transaction. For the original non-nested transaction, thecomputed digest may be updated. Upon an unsuccessful completion of oneor more of the nested transactions, the processor 114 (FIG. 16) mayclear the nesting level computed digest of the unsuccessful nestedtransaction.

Now referring to FIG. 15, flowchart 1500 illustrates steps performed bythe processor 114 (FIG. 16) for nesting digest transactions, within thedata processing environment of FIG. 16. The steps of the flowchart 1500illustrate the generation of a computed digest in which the computeddigest may be updated directly, during the execution of a nested digesttransaction, in accordance with an embodiment of the disclosure. In thisembodiment, the processor 114 (FIG. 16) may start a non-nested, digesttransaction, at 1510. The processor 114 (FIG. 16) may update thecomputed digest for this transaction for each instruction in thetransactional region, at 1515. At 1520, for an instruction in thetransactional region that may be a transaction begin for a nestedtransaction, the processor 114 (FIG. 16) may, at 1525, save a snapshotof the current computed digest as a nesting level snapshot of thecomputed digest. The snapshot of the current computed digest may besaved to a location including, but not limited to, a store buffer, acache, and a software array. The processor 114 (FIG. 16) may increment anesting level count, at 1530, to allow the processor 114 (FIG. 16) toknow when all nested transactions have completed. The processor 114(FIG. 16) may execute each instruction in the nested transaction and, inthis embodiment, update the computed digest with transactional executiondata from the nested transaction, at 1535. For a successfully completednested transaction, as determined at 1545, the processor 114 (FIG. 16)may decrement the nesting level count, at 1550, clear the saved, nestinglevel snapshot of the computed digest at the corresponding nestinglevel, at 1560, and return to the execution of the digest transaction.For the digest transaction that may be a reliability-digest-generatingtransaction, the memory read and write sets of the nested transactionmay be discarded along with the memory updates. For the digesttransaction that may be a reliability-digest-checking transactioninstead, the memory read and write sets of the nested transaction may bemerged into the reliability-digest-checking transaction's memory readand write sets. The nested transaction's memory updates may bediscarded. For an unsuccessfully completed nested transaction,determined at 1545, the processor 114 (FIG. 16) may roll back the memoryupdates of the failed nested transaction, at 1547, restore the computeddigest from the saved, nesting level snapshot of the computed digest, at1555, and retry the nested transaction, at 1535. The processor 114 (FIG.16) may iterate, at 1565, through the remaining instructions in thedigest transaction's transactional region. For an unsuccessfulcompletion of the digest transaction, determined at 1570, the processor114 (FIG. 16) may clear the computed digest, at 1580 and retry thetransaction.

When the digest transaction is not a nested transaction itself andcompletes successfully, as determined at 1570, the processor 114 (FIG.16) may, at 1585, for a digest transaction that is areliability-digest-generating transaction, save the computed digestwhich includes the nested transaction's updates, discard the memory readand write sets, discard the memory updates and restore the initialmachine state. Alternately, the processor 114 (FIG. 16) may, at 1585,for a digest transaction that is a reliability-digest-checkingtransaction whose digests compare successfully, COMMIT the memoryupdates which include the nested transaction's memory updates and returncompletion information to the computer software application. For thesuccessful completion of the digest transaction, determined at 1570,that may itself be a nested transaction, the processor 114 (FIG. 16) maycontinue processing at step 1550 of a transaction at the previoustransaction nesting level of this digest transaction.

With continuing reference to FIG. 15, the steps of the flowchart 1500with the following modifications illustrate the generation of a computeddigest in which the computed digest may be updated only when all nestedtransactions have completed, in accordance with an embodiment of thedisclosure. The processor 114 (FIG. 16), at 1525, may save a snapshot ofthe current computed digest as a nesting level snapshot of the computeddigest and initialize a nesting level computed digest for the nestedtransaction. The processor 114 (FIG. 16) may, at 1535, execute eachinstruction in the nested transaction and, in this embodiment, updatethe nesting level computed digest with transactional execution data fromthe nested transaction. In response to an unsuccessful nestedtransaction, the processor 114 (FIG. 16) may, at 1555, clear the nestinglevel computed digest of the failed transaction in preparation forretry. In response to a successfully completed nested transaction, theprocessor 114 (FIG. 16) may, in this embodiment, at 1560, replace theprevious nesting level transaction's nesting level computed digest witha merge of the nested transaction's nesting level computed digest andthe nesting level snapshot of the computed digest saved prior to thenested transaction. When the nesting level indicates that all nestedtransactions have completed, the computed digest may be updated.

In another embodiment, the nested transaction may be areliability-digest-checking transaction. In this embodiment, theprocessor 114 (FIG. 16) may merge the read sets and write sets of thenested transaction with the read and write sets of the previous nestinglevel transaction and discard the memory updates of the successfullycompleted and successfully executed reliability-digest-checking nestedtransaction. The nested reliability-digest-checking transaction may notCOMMIT the memory updates. For a digest mis-compare in a nestedreliability-digest-checking transaction, the processor 114 (FIG. 16) maytransfer control to a sequence of instruction in the previous nestinglevel transaction that may include, but are not limited to, instructionsto restore the computed digest from the saved nesting level snapshot ofthe computed digest from the previous nesting level.

In at least one embodiment, the sequence of instructions correspondingto the digest mis-compare transfer of control may be written such thatretry attempts may not be incorporated into the computed digest. In oneembodiment, this may be achieved by preventing updates to the digestduring the above sequence of instructions. In another embodiment,explicit DIGEST BEGIN and DIGEST END (FIG. 14) instructions may be usedto disabled the processor 114 (FIG. 16) from updating the digest duringexecution of recovery logic to avoid capturing possible non-replicatableexecution paths through recovery logic as part of the digest.

In another embodiment, a non-digest transaction may be nested within adigest transaction. In this embodiment, when the nested transaction isencountered, it may be processed to completion as described above withreference to FIG. 15, including the updating of the computed digest toinclude the transactional region of the nested transaction. If thenested transaction fails, the nested transaction may be restarted. Whenthe nested transaction completes successfully, the memory read and writesets and the pending memory updates may be merged with the previousnesting level transaction's memory read and write set and pending memoryupdates. Any instrumentation, diagnostic or other execution informationassociated with the nested transaction may also be included in theprevious nesting level transaction's instrumentation, diagnostic orother data. When the previous nesting level transaction is not a nestedtransaction itself and completes successfully, the processor 114 (FIG.16) may for a reliability-digest-checking transaction with a successfuldigest compare, COMMIT the results of the nested transaction inconjunction with the COMMIT of the reliability-digest-checkingtransaction. Alternately, for a successful non-nestedreliability-digest-generating transaction, the processor 114 (FIG. 16)may discard the results of the nested transaction in conjunction withthe discarding of the reliability-digest-generating transaction, and maysave the computed digest (along with any diagnostic, instrumentation, orother execution data) including information from both the digesttransaction and the nested non-digest transaction.

In another embodiment, a digest transaction may be nested within anon-digest transaction. In this embodiment, when the nested digesttransaction is encountered, a computed digest may be initialized andupdated for the instructions in the nested transactional region. If thenested transaction fails, the nested transaction's computed digest maybe reinitialized and the nested transaction may be restarted. For asuccessfully completed, nested reliability-digest-generatingtransaction, the processor 114 (FIG. 16) may merge the memory read andwrite sets of the nested reliability-digest-generating transaction intothe non-digest transaction. The memory updates of the nestedreliability-digest-generating transaction may be discarded. The nestedreliability-digest-generating transaction may save the computed digestas a nesting level reliability digest. In another embodiment, the memoryread and write sets of the nested reliability-digest-generatingtransaction may be discarded along with the memory updates and only thecomputed digest may be saved as a nesting level reliability digest. Foran unsuccessfully completed, nested reliability-digest-checkingtransaction, the nested transaction's computed digest may bereinitialized and the nested transaction may be restarted. For asuccessfully completed, nested reliability-digest-checking transactionwhose digests compare successfully, the processor 114 (FIG. 16) maymerge the memory read and write sets of the nestedreliability-digest-checking transaction into the read and write sets ofthe non-digest transaction. When a digest mis-compare in a nestedreliability-digest-checking transaction occurs, the processor 114 (FIG.16) may transfer control to a sequence of instruction in the non-digesttransaction.

In another embodiment, flattened nesting may be implemented inconjunction with digest transactions. Flattened nesting may allow thenested transactions to be automatically integrated into the outermosttransaction.

Referring now to the nesting of transactions, transactional executionfor reliability can further be practiced in conjunction withtransactional nesting.

In one embodiment, synchronization transactions are included in areliability transaction. In according with the nesting of asynchronization transaction in a reliability transaction, in oneembodiment, flattened nesting is implemented and an interiorsynchronization transaction (i.e., a transaction directed atsynchronizing multiple threads in accordance with prior art) isautomatically integrated in an outer digest generating and digestchecking transaction.

In another embodiment, a synchronization transaction is processed as anested transaction. In this embodiment, when an interior (nested)synchronization transaction is encountered, a currently computedreliability digest is saved to a new storage location. A new reliabilitydigest is initialized for the nested transaction. A reliability digestis computed for the synchronization transaction. The synchronizationtransaction is processed. If the synchronization transaction fails, asynchronization transaction may be restarted. The reliability digest forthe restarted synchronization transaction is reset and a new reliabilitydigest is computed. When the synchronization transaction completessuccessfully, the memory read and write sets' and pending memory updatesare merged in the digest generating or digest checking reliabilitytransaction. Any instrumentation, diagnostic or other executioninformation associated with a nested transaction may also be included inthe outer reliability transaction's instrumentation, diagnostic or otherdata. The stored reliability transaction's reliability digest which hadbeen stored prior to the synchronization transaction is recovered, andpreferably combined with the (successful) synchronization transactionscomputed reliability digest. The so combined and updated new reliabilitydigest is initialized into the current reliability digest for furtheruse by the other reliability transaction. When an outer reliabilitytransaction completes, an outer digest checking reliability transactioncommits the results of the nested synchronization transaction inconjunction with the commit of the outer reliability transaction, whenthe digest compare is successful. When an outer reliability transactioncompletes, an outer digest generating reliability transaction discardsthe results of the nested synchronization transaction in conjunctionwith the discarding of the outer reliability transaction, and present adigest (and any debug, instrumentation, or other execution data)including both an outer reliability transaction and an innersynchronization transaction.

Referring now to the nesting of a reliability digest generatingtransaction, or a reliability digest checking transaction in asynchronization transaction, reliability digest generating andreliability digest checking instructions are preferably processed astrue nested transactions. In this embodiment, when an interior (nested)reliability transaction is encountered, a new reliability digest isinitialized for the nested transaction. A reliability digest is computedfor a reliability digest generating transaction as a nested transaction.If the digest generating transaction fails, a digest generatingtransaction may be restarted. The reliability digest for the restarteddigest generating transaction is reset and a new reliability digest iscomputed. When the digest generating transaction completes successfully,the memory read and write sets are merged into the synchronizationtransaction, and the memory updates are discarded. The reliabilitydigest is returned. In another embodiment, the memory read and writesets are discarded and the memory updates are discarded. The reliabilitydigest is returned.

A reliability digest is computed for a reliability digest checkingtransaction as a nested transaction. If the digest checking transactionfails, a digest checking transaction may be restarted. The reliabilitydigest for the restarted digest checking transaction is reset and a newreliability digest is computed. When the digest checking transactioncompletes successfully, and the digest comparison indicates a reliableexecution, the memory read and write sets and the memory updates aremerged into the synchronization transaction. When a digest miscompares,control is transferred to a digest miscompare logic executed as asequence of computer instructions within the synchronizationtransaction.

Referring now to the nesting of a reliability digest generatingtransaction, or a reliability digest checking transaction in areliability digest generating or reliability digest comparingtransaction, reliability digest generating and reliability digestchecking instructions are preferably processed as true nestedtransactions. In this embodiment, when an interior (nested) reliabilitytransaction is encountered, the current reliability transactions digest(for both digest generating and digest checking cases) is stored, and anew reliability digest is initialized for the nested transaction. Areliability digest is computed for a reliability digest generatingtransaction as a nested transaction. If the digest generatingtransaction fails, a digest generating transaction may be restarted. Thereliability digest for the restarted digest generating transaction isreset and a new reliability digest is computed. When the digestgenerating transaction completes successfully, the memory read and writesets are merged into the outer reliability transaction, and the memoryupdates are discarded. The reliability digest is returned. The savedreliability digest of the outer transaction is recovered andreinitialized to accrue additional results. In another embodiment, thememory read and write sets are discarded and the memory updates arediscarded. The reliability digest is returned. The saved reliabilitydigest of the outer transaction is recovered and reinitialized to accrueadditional results.

A reliability digest is computed for a reliability digest checkingtransaction as a nested transaction in a reliability transaction. Inthis embodiment, when an interior (nested) reliability transaction isencountered, the current reliability transactions digest (for bothdigest generating and digest checking cases) is stored, and a newreliability digest is initialized for the nested transaction. If thedigest checking transaction fails, a digest checking transaction may berestarted. The reliability digest for the restarted digest checkingtransaction is reset and a new reliability digest is computed. When thedigest checking transaction completes successfully, and the digestcomparison indicates a reliable execution, the memory read and writesets and the memory updates are merged into the reliability transaction.The outer transactions saved digest is recovered. The inner reliabilitytransaction checking transaction's digest is merged into the outerrecovered digest. The so computed digest is reinitialized and used bythe outer transaction. When a digest miscompares, control is transferredto a digest miscompare logic executed as a sequence of computerinstructions within the synchronization transaction. The outer digest isrecovered, and restored. The reliability checking transaction's digestis not merged into the outer transaction's digest.

In at least one embodiment, the sequence corresponding to the digestmiscompare recover is written to avoid different digest results based onthe number of retries. In one embodiment, this is achieved by avoidingupdates to state included in the digest. In another embodiment, explicitdigest_on and digest_off are provided. When miscompare recovery logic isexecuted, digest generation is disabled by executing recovery logicwithin pairs of digest_off and digest_on instructions to avoid capturingdifferent execution paths through recovery logic as part of the digest.

When an outer reliability digest generating transaction completes, allmemory updates are discarded and a digest including inner transactionsis provided.

When an outer reliability digest checking transaction completes and thedigest compares successfully, all memory updates are committed tomemory, and including those of inner transactions having been mergedinto an outer transaction.

Referring now to FIG. 16, computer system 1600 may include respectivesets of internal components 800 and external components 900. Each of thesets of internal components 800 includes one or more processors 114; oneor more computer-readable RAMs 822; one or more computer-readable ROMs824 on one or more buses 826; one or more operating systems 828; one ormore software applications 829; and one or more computer-readabletangible storage devices 830. The one or more operating systems 828 arestored on one or more of the respective computer-readable tangiblestorage devices 830 for execution by one or more of the respectiveprocessors 114 via one or more of the respective RAMs 822 (whichtypically include cache memory). The computer system 1600, in oneembodiment of the disclosure, supports the multicore transactionalmemory environment and TM-enabled processors of FIG. 1. FIG. 16illustrates the TM-enabled processors of FIG. 1, shown in the context ofa computer system, as processors 114 of the computer system 1600. Theprocessors 114, in this embodiment, are also configured to identify thereliable-execution instructions (FIGS. 8-13) and are enabled to checkthe reliability digest. The processors 114 are also connected by one ormore Digest Broadcast Buses 650 configured to communicatereliable-execution information. In the embodiment illustrated in FIG.16, each of the computer-readable tangible storage devices 830 is amagnetic disk storage device of an internal hard drive. Alternatively,each of the computer-readable tangible storage devices 830 is asemiconductor storage device such as ROM 824, EPROM, flash memory or anyother computer-readable tangible storage device that can store acomputer program and digital information.

Each set of internal components 800 also includes a R/W drive orinterface 832 to read from and write to one or more computer-readabletangible storage devices 936 such as a CD-ROM, DVD, SSD, memory stick,magnetic tape, magnetic disk, optical disk or semiconductor storagedevice.

Each set of internal components 800 may also include network adapters(or switch port cards) or interfaces 836 such as a TCP/IP adapter cards,wireless WI-FI interface cards, or 3G or 4G wireless interface cards orother wired or wireless communication links. The firmware 838 andoperating system 828 that are associated with computer system 1600, canbe downloaded to computer system 1600 from an external computer (e.g.,server) via a network (for example, the Internet, a local area networkor other, wide area network) and respective network adapters orinterfaces 836. From the network adapters (or switch port adapters) orinterfaces 836, the firmware 838 and operating system 828 associatedwith computer system 1600 are loaded into the respective hard drive 830and network adapter 836. The network may comprise copper wires, opticalfibers, wireless transmission, routers, firewalls, switches, gatewaycomputers and/or edge servers.

Each of the sets of external components 900 can include a computerdisplay monitor 920, a keyboard 930, and a computer mouse 934. Externalcomponents 900 can also include touch screens, virtual keyboards, touchpads, pointing devices, and other human interface devices. Each of thesets of internal components 800 also includes device drivers 840 tointerface to computer display monitor 920, keyboard 930 and computermouse 934. The device drivers 840, R/W drive or interface 832 andnetwork adapter or interface 836 comprise hardware and software (storedin storage device 830 and/or ROM 824).

Referring now to FIG. 17, in an embodiment of the disclosure,diagnostics may be gathered during a transactional execution in atransactional memory environment where memory store data of thetransaction may be committed to memory at transaction completion. Acomputer system may, at 1710, identify a first indicator that may signala beginning instruction of a transaction comprising a plurality ofinstructions. The computer system may then, at 1720, generate a computeddigest based on the execution of at least one of the plurality ofinstructions. The computed digest may be generated by a HASHingalgorithm, hashing at least one of: memory store operand data of theplurality of instructions, memory read operand data of the plurality ofinstructions, and register store operand data of the plurality ofinstructions. In another embodiment, generating the computed digest mayinclude updating the computed digest with data provided by one or morespecialized instructions in the plurality of instructions specifyingdata to be included in the digest. Diagnostic data of the transactionbased on the execution of the plurality of instructions may beaccumulated, at 1730. The accumulated diagnostic data may include anyone of a transaction progress indication, a reason for the transactionabort, an address causing the abort, an instruction that encountered anexecution failure, a list of transactional execution memory updates, alist of transactional execution memory addresses or a list oftransactional execution instructions. Upon identifying, at 1740, asecond indicator associated with the plurality of instructions signalingan ending instruction of the transaction, and based on an abort of thetransaction, at 1750, saving the computed digest and the diagnostic dataand not saving the memory store data of the transaction to memory. Anabort of the transaction may be caused by the computed digest notmatching a previously saved computed digest of a previous transaction.

In another embodiment, the computed digest may be generated uponidentifying the second indicator and may be based on a final snapshot ofdata buffered during the transaction for commitment.

Various embodiments of the invention may be implemented in a dataprocessing system suitable for storing and/or executing program codethat includes at least one processor coupled directly or indirectly tomemory elements through a system bus. The memory elements include, forinstance, local memory employed during actual execution of the programcode, bulk storage, and cache memory which provide temporary storage ofat least some program code in order to reduce the number of times codemust be retrieved from bulk storage during execution.

Input/Output or I/O devices (including, but not limited to, keyboards,displays, pointing devices, DASD, tape, CDs, DVDs, thumb drives andother memory media, etc.) can be coupled to the system either directlyor through intervening I/O controllers. Network adapters may also becoupled to the system to enable the data processing system to becomecoupled to other data processing systems or remote printers or storagedevices through intervening private or public networks. Modems, cablemodems, and Ethernet cards are just a few of the available types ofnetwork adapters.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Java, Smalltalk, C++ or the like,and conventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

Although one or more examples have been provided herein, these are onlyexamples. Many variations are possible without departing from the spiritof the present invention. For instance, processing environments otherthan the examples provided herein may include and/or benefit from one ormore aspects of the present invention. Further, the environment need notbe based on the z/Architecture®, but instead can be based on otherarchitectures offered by, for instance, IBM®, Intel®, Sun Microsystems,as well as others. Yet further, the environment can include multipleprocessors, be partitioned, and/or be coupled to other systems, asexamples.

As used herein, the term “obtaining” includes, but is not limited to,fetching, receiving, having, providing, being provided, creating,developing, etc.

The flow diagrams depicted herein are just examples. There may be manyvariations to these diagrams or the steps (or operations) describedtherein without departing from the spirit of the invention. Forinstance, the steps may be performed in a differing order, or steps maybe added, deleted, or modified. All of these variations are considered apart of the claimed invention.

Although preferred embodiments have been depicted and described indetail herein, it will be apparent to those skilled in the relevant artthat various modifications, additions, substitutions and the like can bemade without departing from the spirit of the invention, and these are,therefore, considered to be within the scope of the invention, asdefined in the following claims.

What is claimed is:
 1. A method for gathering diagnostics during atransactional execution in a transactional memory environment forperforming transactional executions, wherein memory store data of atransaction are committed to memory after transaction completion, themethod comprising: identifying, by a computer system, a beginninginstruction of a transaction, the transaction comprising a plurality ofinstructions; identifying, by the computer system, an ending instructionof the transaction; generating, by the computer system, a computeddigest based on a digest generating algorithm operating on invariantdata in one or more executed instruction of the transaction;accumulating, by the computer system, diagnostic data of the transactionbased on the executed instructions of the transaction, wherein thediagnostic data includes the computed digest and one or more of: a listof instructions used in the generation of the computed digest; atransaction progress indicator; a list of transactional execution memoryaddresses; an instruction that encountered an execution failure; and areason for the execution failure; and upon completion of thetransaction, determining whether the computed digest matches apreviously saved computed digest that is based on the digest generatingalgorithm operating on the invariant data in a previous completion ofthe transaction; based on the computed digest not matching thepreviously saved computed digest: aborting of the transaction; saving,by the computer system, the diagnostic data; and not saving the memorystore data of the transaction to memory.
 2. The method according toclaim 1, wherein the computed digest is generated by a HASHingalgorithm, hashing at least one of: memory store operand data of theplurality of instructions; memory read operand data of the plurality ofinstructions; and register store operand data of the plurality ofinstructions.
 3. The method according to claim 1, wherein theaccumulated diagnostic data further comprises one or more of: a reasonfor a transaction abort; an address causing the abort; and a list oftransactional execution memory updates.
 4. The method according to claim1, wherein generating the computed digest comprises generating thecomputed digest upon identifying the second indicator and based on afinal snapshot of data buffered during the transaction for commitment.